ubuntu randomly freezes

[MHayes]

Linux test-pc 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

I'm running Ubuntu 7.04 Feisty Fawn and have been encountering random freezes since the day I installed it. The only way to recover from these freezes is through a hard reboot. I had previously used Ubuntu 6.10 Edgy Eft and never had any issues. I'm currently using Beryl + XGL using the fglrx driveron an ATI Radeom ATI X1600, but the freezes were occuring even with the default open source vesa driver ... so I don't think it's neccessarily Beryl causing the issue. I've also tried using both wireless and wired internet connections and had the same issue. Here are some other things that I've tried:

- adding noapic to my boot options (which made the freezes occur less frequently)
- disabled /etc/init.d/powernowd (not sure if this did anything)
- disabled beryl + xgl and used vesa driver, but this didn't make a difference
- also tried connected via ethernet instead of wireless which didn't make a difference

I can't seem to pinpoint any particular one thing that is causing this freezing issue. I'm going to include some additional information below, let me know if you need any other information, thanks.

[Thomas Hallgren (thomas-h)]

This sounds very similar to my experience with feisty. I had been using feisty since the middle of January and I think the problem started around kernel version 2.6.20-9.

I have not seen the problem after switching back to edgy. I am currently using Fedora 7 test 4, and I don't get any random oopses or crashes here either. So I don't think it is a hardware problem.

I filed a bug report about a month ago:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108953

This bug also sounds similar:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85500

[candtalan (aeclist)]

Am using a clean install of kubuntu 7.04 (today) (June 4th 2007), after a year of 6.06 kubuntu with no problems. Suddenly today, several freezes. Only firefox has been installed aferr full new install and updates. (firefox is not being used wwhen freezes have occurred).
Wired ethernet only,

The only unusual thing I can I note about this machine today is - when running apparently ok, and ctrl alt backspace used (as a test) then the xserver does not re start and offer a new login, although I can then use crtl F1 to get terminal and shutdown.

lsmod as follows (hth)

user@dabs1:~$ lsmod
Module Size Used by
rfcomm 40856 0
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
ppdev 10116 0
speedstep_lib 6148 0
cpufreq_stats 7360 0
cpufreq_userspace 5408 0
cpufreq_conservative 8200 0
cpufreq_powersave 2688 0
cpufreq_ondemand 9228 0
freq_table 5792 2 cpufreq_stats,cpufreq_ondemand
tc1100_wmi 8068 0
dev_acpi 12292 0
pcc_acpi 13184 0
sony_acpi 6284 0
battery 10756 0
ac 6020 0
button 8720 0
video 16388 0
sbs 15652 0
container 5248 0
dock 10268 0
asus_acpi 17308 0
i2c_ec 6016 1 sbs
backlight 7040 1 asus_acpi
ext2 66824 1
reiserfs 247680 3
ipv6 268960 8
lp 12452 0
fuse 46612 0
snd_intel8x0 34332 4
snd_ac97_codec 98464 1 snd_intel8x0
ac97_bus 3200 1 snd_ac97_codec
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
snd_pcm 79876 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
parport_pc 36388 1
parport 36936 3 ppdev,lp,parport_pc
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_m
idi_event
snd_timer 23684 3 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmi
di,snd_seq
serio_raw 7940 0
iTCO_wdt 11812 0
iTCO_vendor_support 4868 1 iTCO_wdt
i2c_i810 6276 0
pcspkr 4224 0
psmouse 38920 0
i2c_algo_bit 8712 1 i2c_i810
snd 54020 16 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mix
er_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 8672 1 snd
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm
intel_agp 25244 1
agpgart 35400 1 intel_agp
i2c_core 22656 3 i2c_ec,i2c_i810,i2c_algo_bit
shpchp 34324 0
pci_hotplug 32576 1 shpchp
af_packet 23816 4
tsdev 8768 0
evd...

[Zenigata (drebon)]

Kind of the same problem, think it has been reporter in xorg's bug tracker as well (I just do not find the reference right now but there are similar bugs).

I think it happens less frequently when using the ati driver instead of the fglrx driver, but I do not guaranty a fail saif. It has nothing to do (by me) with Beryl/Compiz or XGL.

Someone on Xorg's bug tracker emitted the possibility for it to be a memory leak than can possibly occur with any driver, but that where some kind of speeded up using some particular drivers or doing particular things (intensive windows resizing has been reported to be likely to help the bug to occurs).

I tried upgrading xorg to the gutsy's one, the I have a bug that prevent me from using the 3D in fglrx, but I seem to have much more frequent freezes with ati's proprietary driver (just for the 2D part) than with the free xorg driver "ati".

When freeze occurs, cpu raise to 100% (both cores), if I have the time, I can stop the freeze by killing xorg (one to five seconds to understand that there's going to be a freeze and react).

The mouse is still alive, but I'm not able to switch to another terminal. Some tells that it i possible to connect to the host via ssh and kill xorg to get out of the freeze.

[Gregor Goestl (gregor-goestl)]

I have similar problems:

I'm running feisty (upgraded it from edgy). But I have a NVIDIA card. Beryl with XGL is installed, but KWin as window manager is loaded, not Beryl.
After a few minutes (15-20) leaving my computer the freeze happens. Programmes like Amarok (while playing music) and Azureus still work, but I cannot press any buttons and do mouse clicks. Pressing the Power-Button on my computer's case shows the Logout / Shutdown / ... buttons.

So my Linux isn't usable for me at the moment!

[Gregor Goestl (gregor-goestl)]

Here you can see my /var/log/messages from start and the restart after the reboot.

[Sitsofe Wheeler (sitsofe)]

Gregor:
This is probably the wrong bug to report your particular issue. There's a very small chance given that you are using an AMD that you are seeing Bug #109643 . Further, since you are using manually installed NVIDIA drivers (100.14.09) unless you can reproduce the problem with the open source nv driver then your support options have changed as you are using an NVIDIA package not distributed by Ubuntu. Any problems that occur after installing drivers not provided by Ubuntu repositories should not be reported to the launchpad bug area. If the drivers were downloaded from the NVIDIA web site then the NVIDIA Linux web forum (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 ) is an appropriate place to report issues. If a 3rd party installer was used please contact the 3rd party for support. Other places for manual driver support can be found on the Community Support page (http://www.ubuntu.com/support/communitysupport ).

[Zenigata (drebon)]

I was wondering, could it be possible to have a running daemon with quite a high priority that just kill worg if it is using too high cpu ressource for a too long time ? I know this would not be a solution, but more a work around, but it will also allow one to have more logs I think (I think it writes a little more when it is killed than when it receives an irq emergency stop call)

[Gregor Goestl (gregor-goestl)]

It doesn't sound like Bug #109643 ...
I didn't try the nv, because of my two monitors (TwinView). The Nvidia driver provided as Ubuntu package didn't work for me. (I also had problems with this package on kernel updates in edgy ...)

I changed my configuration, that Beryl isn't started at kdm login. So only the window borders and taskbar go away, but I'm able to restart X (keyboard and mouse clicks are working).

I know, that there is no support for external Nvidia drivers, but is there any way to get more information about the crash of KWin?

[Sitsofe Wheeler (sitsofe)]

Gregor:
If you are seeing KWin problems you are definitely better off filing a new bug report in launchpad that can eventually make its way to the KDE developers. They won't come looking for the issue over here...

Again it is worth testing with the nv driver. I know it doesn't do Twinview but if the problem doesn't occur on the single head with the nv driver but it does with the NVIDIA binary only driver then it strongly suggests that the problem lies with the NVIDIA driver and you are better off talking to NVIDIA. If the problem DOES occur with the nv driver then it suggests you have a generic xorg or KWin problem.

[Patrick Salami (pat-entitycom)]

I have the exact same problem with X taking 100% CPU after sitting idle for a while.
If this is the case for you, then you are most likely experiencing bug 109507 and bug 120347.

[Leann Ogasawara (leannogasawara)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue? Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download? Please report back your results. If the issue is still present in the new release, please attach the information outlined in the kernel team bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies. Also, please attach each file as a separate attachement. Thanks again and we appreciate your help and feedback.

[Wallace C. Olson Jr. (wolsonjr)]

Gutsy is fine. There are NO lockups.
Everything appears good except wireless (Toshiba laptop with Atheros
wireless).
Wally

On Thu, 18 Oct 2007 11:44:25 -0500, Leann Ogasawara <email address hidden>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out,
> we were wondering if you can still reproduce this issue? Could you
> please download and try the new version of Ubuntu from
> http://www.ubuntu.com/getubuntu/download? Please report back your
> results. If the issue is still present in the new release, please
> attach the information outlined in the kernel team bug policy at
> https://wiki.ubuntu.com/KernelTeamBugPolicies. Also, please attach each
> file as a separate attachement. Thanks again and we appreciate your
> help and feedback.
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Status: New => Incomplete
>

--
t'ai chi-linux-bach-go

[Lorin Ricker (lorin)]

I am having this problem -- just started a couple of days ago on a 4-week old ("semi-fresh") GG 7.10 installation (dual-boots w/ W2K on a Compaq desktop, AMD Athlon CPU, 64MB, 2 IDE disks w/ 2 partitions for Linux and 2 for Windows, ATI Radeon 9250 display adapter). This "random freezes" problem seems, to me, to be a critical bug, impacting Ubuntu availability, reliability and integrity -- It also seems to be showing up in several/various Bug Reports in various descriptions and forms, but these all seem, at the bottom, related.

There is a very extensive Ubuntu Forums thread, http://ubuntuforums.org/showthread.php?t=412125, "feisty fawn freezes ! driving me insane", with well over 800 posts referring directly to this problem. Support/developers may want to "data mine" this thread for additional anecdotal evidence, if not already done so...

This problem "randomly freezes" is pervasive and widespread across multiple hardware (e.g., nvidia *and* ATI/Radeon cards, desktops and laptops, Intel and AMD cpus, etc.), releases (feisty and gutsy, at least -- yes, *many* 7.10 users are currently experiencing the problem), and seems largely independent of what, precisely, the user was doing when the next *random* freeze/hang/lock-up occurs (e.g., compriz, firefox, printing, "typing quickly", or just "mousing around").

Various postings on that thread recommend a wide variety of workarounds and "fixes" for the problem -- judging from that anecdotal evidence, no one thing seems to work, or even to pin-point the problem.

This Bug #117651, together with that Forums thread#412125, all seem also related to Bugs #103400 (compiz freezes x server after screensaver kicks in), #108527 (X freezes when compiz is enabled on ATI cards), and #120347 (xorg hang after longer (12h) idle time), at a minimum -- there may be other bug reports that are directly related, tho' using different words/symptoms to describe the same overall problem.

Shameless admission: I'm a Linux newbie here -- but I do have over 25 years of sw-dev experience on mainframes and mini's (VMS -- yes, probably mostly irrelevant here! ;-) ) -- and it just seems to me that tying awareness of these Bugs (and others?), together with the above-ref'd Forum thread, would be helpful in resolving this critical "random freeze" problem for all of us. Respectfully -- Lorin

[michal przadka (przadka)]

Ive just installed GG on my parents PC. They got really excited with Ubuntu but after a few days complaining about random freezes :(

Its AMD with an ATI card. Can provide more info if needed.

[Leann Ogasawara (leannogasawara)]

Hi Lorin and Michal,

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. Thanks.

[Lorin Ricker (lorin)]

Hi, Leann -- Many thanks for your response! Yes, I'll get HH-alpha
downloaded and burned to LiveCD; however, as I'm not certain that
running LiveCD would trigger the problem, and whereas my current
dual-boot PC is, at this point, a test-bed only (I've not been able to
move into a "regular use" status on this PC due to this very bug), I'll
likely just upgrade on-disk, and then give it a full-blown shot at
hanging my system again...

Unless you have specific counter-reasons and advice why I shouldn't do
this? Please let me know.

Also, I doubt that I'll have any results at all to post back to you, as
we're leaving town on over-the-weekend business this Thursday... It may
be a couple of weeks before you hear feedback from me on this, OK?

warmest regards,
   -- Lorin

Lorin Ricker
10781 Holden Circle
Franktown, CO 80116

    cell: [phone]
email: <email address hidden>

On 3/10/2008 9:45 AM, Leann Ogasawara wrote:
> Hi Lorin and Michal,
>
> The Hardy Heron Alpha series is currently under development and contains
> an updated version of the kernel. It would be helpful if you could test
> the latest Hardy Alpha release: http://www.ubuntu.com/testing . You
> should be able to then test the new kernel via the LiveCD. If you can,
> please verify if this bug still exists or not and report back your
> results. Thanks.
>

[LEVIS Cyril (atlas95)]

I had 3 freeze too with ubuntu hardy since 2 days.
My light screen gone black and led bling bling.
I must force poweroff and restart...I have any ideas but with gutsy I havn't this.

[Lorin Ricker (lorin)]

Hi, Leann! After our out-of-towner, I had some time last week & weekend
to give the HH-alpha distro (LiveCD) a test-run -- here's my results,
plus some questions:

1. I downloaded v8.04 and burned it...

2. Booted the LiveCD on Friday evening at approx. 10:00pm

3. As it was never very difficult (only unpredictable as to exactly
when) to experience a system-freeze with v7.10 -- and it didn't seem to
matter what I was doing, e.g., bash/com-window, Firefox surfing, playing
a game, etc. -- I decided to simply play mah-jong until either the
freeze happened again or I got tired. ;-)

4. After about 90 minutes, I got tired (had better things to do that
late at night), so...

5. I left v8.04 running (from the LiveCD), just let it go to
screen-saver, intending to get back to it the following morning
(Saturday). But I didn't...

6. Instead, I left the PC running (screen-saver) all weekend, only
returned to it this evening (Monday), approx. 70 hours later. Eager to
see: was it frozen? v7.10 would'a been, without question.

7. Nope, er, yup -- v8.04 was *not* frozen! Hooray -- small victory!

8. I went ahead and ran/played mah-jong again for about 20 minutes,
thinking that maybe I could tip it over its edge... stayed solid &
working until I shut it down.

So, apparently v8.04 is not as prone to freezing as was v7.10 -- Yes,
I'm a skeptic, from experience in debugging other kinds of interactive
systems. It's very hard to "prove the negative", i.e., "it *won't ever*
freeze"... Only long, hard hours of actual use will build that kind of
confidence.

But there's your early test result -- v8.04 did not freeze on my PC
(where 7.10 would routinely, unpredictably freeze, usually within a
couple of hours after (re)boot) after a period of over 70 uptime hours,
with light interactive use. To me, promising but inconclusive.

I'd wonder what the developers would think about this test result... Is
it usefully indicative of a solution to this "my system randomly
freezes" problem? Can my own testing "technique" (mah-jong!) be
improved to give it actually a better shakedown trial?

Any advice as to what should be next? Given the unusability of my
current v7.10 install on this PC (and my desire to actually start using
Linux/Ubuntu with a vengeance, both for personal learning and to
undertake my efforts to ultimately replace Windows throughout my
home-office & family's PCs):

a) Should I next proceed to install v8.04 from the LiveCD, with the
understanding that it's an Alpha release?

b) If so, what limitations and/or issues should I be prepared to deal
with (other than the recurrence of the system-freeze problem under
more-than-light use)? In particular, would I be able to deploy various
common utilities and applications (e.g., Emacs, Open Office,
virt-machines, WINE, etc.), with the understanding that the platform is
indeed pre-release and unstable?

c) If I understand Ubuntu's release terminology, the Hardy Heron v8.04
is scheduled for final release in early August 2008, right? So my own
liabilities would likely include occasional alpha-, and later beta-,
release updates, right, up to the final release? And how often migh...

[Leann Ogasawara (leannogasawara)]

Hi Guys,

LEVIS Cyril - what version of the Hardy kernel are you running (cat /proc/version_signature)

Lorin, thanks for testing and the feedback. Hopefully I can answer your questions:

a) We actually just released the Hardy Beta version - http://www.ubuntu.com/testing . It is always noted that "Pre-releases of Hardy are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu developers and those who want to help in testing, reporting, and fixing bugs." The great thing about the LiveCD's is you can take the latest release for a test drive to help you determine if you'd really like to install and help test the bleeding edge. Ultimately it's your call if you want to install.

b) See http://www.ubuntu.com/testing for a outline of new features as well as known issues with each release.

c) Actually Hardy final is set to come out next month, April 2008, hence the release version being set to 8.04. The Intrepid Ibex 8.10 release will be scheduled to come out in October 2008. The Hardy release schedule can be seen here: https://wiki.ubuntu.com/HardyReleaseSchedule and the subsequent Intrepid release schedule is here: https://wiki.ubuntu.com/IntrepidReleaseSchedule.

d) If you do choose to install and want to help with testing, in addition to what you originally did, you can also take a look at the following for more ideas - https://wiki.ubuntu.com/Testing/Cases.

[Lorin Ricker (lorin)]

Thank you, Leann, for your detailed and helpful response!

a) I understand -- I'm just in "eval mode" myself, so working with beta
software is not an issue. Is it safe to assume that, at Final Release
in April, all repository components will be checked out and ready to go
for 8.04?

b) & d) Great new features -- and the /testing pages are *very* helpful.

c) Oh. 8.04 stands for "2008 April", not "August 4th" -- duh. Got it!
  Um, is there a "new features" page for Intrepid/8.10 yet?

I'm downloading 8.04 Desktop and Alternate iso's now -- Will test LiveCD
and install & test -- and will report as needed.

Thanks again, Leann!

warmest regards,
   -- Lorin

On 3/25/2008 9:18 AM, Leann Ogasawara wrote:
> Hi Guys,
>
> LEVIS Cyril - what version of the Hardy kernel are you running (cat
> /proc/version_signature)
>
> Lorin, thanks for testing and the feedback. Hopefully I can answer your
> questions:
>
> a) We actually just released the Hardy Beta version -
> http://www.ubuntu.com/testing . It is always noted that "Pre-releases
> of Hardy are *not* encouraged for anyone needing a stable system or
> anyone who is not comfortable running into occasional, even frequent
> breakage. They are, however, recommended for Ubuntu developers and
> those who want to help in testing, reporting, and fixing bugs." The
> great thing about the LiveCD's is you can take the latest release for a
> test drive to help you determine if you'd really like to install and
> help test the bleeding edge. Ultimately it's your call if you want to
> install.
>
> b) See http://www.ubuntu.com/testing for a outline of new features as
> well as known issues with each release.
>
> c) Actually Hardy final is set to come out next month, April 2008,
> hence the release version being set to 8.04. The Intrepid Ibex 8.10
> release will be scheduled to come out in October 2008. The Hardy
> release schedule can be seen here:
> https://wiki.ubuntu.com/HardyReleaseSchedule and the subsequent Intrepid
> release schedule is here:
> https://wiki.ubuntu.com/IntrepidReleaseSchedule.
>
> d) If you do choose to install and want to help with testing, in
> addition to what you originally did, you can also take a look at the
> following for more ideas - https://wiki.ubuntu.com/Testing/Cases.
>

[Krishna E. Bera (keb)]

i was getting random freezing for almost two years and a few upgrades of xubuntu.
it seemed to be associated only with running bittorrent for long periods of time or perhaps the screensaver trying to start.
3 weeks ago i upgraded my power supply and noticed that on the old one the -5V line was dead (or too weak),
and since then i have had no freezing at all, even with 24/7 bittorrent, tor and apache servers running.

[Leann Ogasawara (leannogasawara)]

MHayes,

Since you are the original bug reporter, can you comment if this is still an issue for you with the Hardy Heron 8.04 release? Thanks.

[kiev1 (sys-sys-admin)]

if You see in /var/log/syslog ata error messages after copy large (2Gb) files
then this kernel bug -> http://bugzilla.kernel.org/show_bug.cgi?id=9115#c18

[Aswarp (aswarp2002)]

Have a look to this thread:
https://bugs.launchpad.net/ubuntu/+bug/219345

[Odrodzona-Sarmacja (odrodzona-sarmacja)]

My freezes occured started in april, when I was doing an update of software on my Fiesty, so these freezes came to me during april. Since then I went over to Hardy and I am waiting for official patch to this issue during next 2 years and still waiting.

The packages that cause the freeze is called "Simple DirectMedia Layer" and is named "libsdl1.2debian" and "libsdl1.2image". The freeze affects only keyboard, mouse, screen and sound and leaves everything else running and working just fine despite the freeze. It affects all Linux games (not only 3d games but also even these 2d), apps using 3d rendering and opengl graphics and all apps like firefox using graphic through python engine, which uses SDML in its turn.

Installing older version of "libsdl1.2debian" and "libsdl1.2image" caused freezes to be even more fierce and happening even more often and quicker.

Also used by SDML directly for graphic is package "libpng12-0", which causes freezes on its own and is a security risk on its own in versions prior to 1.2.27. I would sugest making "libpng12-0" a high priority patch for Hardy due these reasons. However installing "libpng12-0" in version 1.2.27 doesn't remove freezes.

My solution to avoid freezes was a removal of Network Manager and do stuff offline. Without Network-Manager and being offline I have no freezes. It seems Network-Manager is the sole reason, which is causing these freezes, when computer is offline from internet. Every time I connect to internet I get unfortunately freezes again even without Network-Manager.

I use VIA motherboard and these mobo are not generally good for Linux and therefore it may be a reason I have these freezes at all. I strongly suspect that networking in general has essential part in causing these freezes and must therefore somehow be on collision with SDML software. Also when I am using nvidia-glx-new binary, as it makes freezes happen less often. I don't know why, but removing vbetool makes sometimes freezes become just a crash-to-desktop event, but just sometimes.

[Odrodzona-Sarmacja (odrodzona-sarmacja)]

Removing network-manager and working offline is a great way of getting rid of freezes. BUT
There are few methods to make freezes less frequent, when networking:

1. Removing&Purging Network-Manager method
2. Setting "highres=off nohz=off irqpoll" options in kernel line in /boot/grub/menu.lst
3. Disabling all cashing for CPU, graphic, shadow memory BIOS and etc in BIOS setting.
4. Installing video card with more memory like 512mb for example (I didn't test it yet, but I did ordered new hardware)

I just recalled that someone in forum
"Ubuntu Forums > The Ubuntu Forum Community > Main Support Categories >Hardware & Laptops"
wrote to me that he installed some "berkelay" (or something sounding like that) networking system in place of the Ubuntu OS networking system and that kept his CPU use constantly over 50%, but removed totally freezes from his computer. I didn't try it and keeping CPU usage constantly over 50% does not sound like fun to me either. But worth mentioning I think for real desperate people.

[Aswarp (aswarp2002)]

I no longer got freezes, but am not sure exactly why. Maybe apt-get dist-upgrading has something to do with it :)
Anyway, thank you for fixing this, I was getting crazy

[Odrodzona-Sarmacja (odrodzona-sarmacja)]

I just bought new hardware and right now It looks like these freezes are no more. What I changed:

CPU: AMD athlon xp -> INTEL e8500
MOBO: VIA -> ASUS
ACCELERATOR: LEADTEK NVIDIA -> ASUS NVIDIA

Maybe it will be of some help.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[sureinlux (sureinlux)]

I have a Compaq Presario V3029au series laptop with AMD Turion x64 and Nvidia chipset. This also used to randomly hang. After much Googling this thread solved the random hanging. http://www.nvnews.net/vbulletin/showthread.php?t=58498 Basically add idle=poll to boot options. Please note that this increases the core temperatures significantly. But the random freezes never happened after that.

Hope this helps.

[Karol Hevessy (khevessy)]

I have to confirm this. It happened to me today (1.10.2008) I'm using Ubuntu Intrepid Alpha-6. The computer suddendly freezed completely. There was nothing to do except for turning it off.

[Ketil Vestby (ketil-vestby)]

On my machine, running Intrepid Beta, this did happend regularily until I installed the server kernel.

After that, it dont freeze anymore. I believe it could be related to some of the differences between the kernels - but it's hard to pinpoint exactly what makes random things disappear..

[Leann Ogasawara (leannogasawara)]

Hi Everyone,

For those of you still experiencing issues with Intrepid, care to open a new report? I feel that even though people may be experiencing the same issue reporter here that it really may be hardware specific. I think it would be better, and additionally more helpful to the kernel team, if you would open a new report specifically for your hardware. For now I'm going to set this particular bug to Incomplete until we get further feedback from MHayes, the original bug reporter.

[Tom Jaeger (thjaeger)]

If you're running intrepid and have an intel 4965 wireless adapter, it is likely that you are experiencing bug #276990.

[Iriiko (aderach)]

Hi!

I have this problem too: Ubuntu freezes and a reboot is needed!!!!
I discover that It freezes when I use Firefox. Flash may cause it I think.
It can hang without doing anything!

So I try to use Opera instead, and no freeze since a week.

Intrepid, Kernel 2.6.27-14

[kiev1 (sys-sys-admin)]

and for me also same, but only on one computer
...uninstall flash and resolve this proble

[Tormod Volden (tormodvolden)]

Please no more "me-too" here, rather file your own bug, and attach information such as /var/log/Xorg.0.log, dmesg and lspci -vvnn output. "apport-cli -f -p linux" will automatically add useful information, but you will need to add Xorg.0.log yourself.

[Steve Conklin (sconklin)]

This bug report is being closed because it was originally opened against a release that is no longer supported, and has caught several 'me too' reports with insufficient information.

If this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04, then please open a new bug.

As stated in the last update, "apport-cli -f -p linux" will automatically add useful information, but you will need to add Xorg.0.log yourself.