system crash, whole system freezes

this is exactly the same as the user above for my machine using Ubuntu 7.10 (Gutsy Gibbon) in Gnome mode

Same as original post. Problem started with Feisty and continues in Gutsy. Never occurred in Dapper. In my case, I do use the smartlink drivers for my modem, but I'm not sure if that has anything to do with it.

If you have Windows NTFS drives in your system, try unmounting them. I think Feisty and Gutsy added NTFS drive write support and sometimes scanning the drives takes a long time--appearing that your machine has locked up. Right-Click, Unmount, then see how long your system stays up.

Original reporter didn't specify what version of Ubuntu he's using. Maybe you should run a memory test. Is this bug still occurring?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

just catched system freeze twice, second was just after reboot and launching few apps(apache, mysql, Zend Studio, firefox, pidgin)

no dumps in logs.

ubuntu jaunty 9.04

When I moved up to Version 8.04 of Ubuntu, this bug stopped, presumably, whatever had caused the bug in version 7.10 had been fixed by an update.

I am now on Jaunty Jackalope (Version (9.04) and most of the bugs are gone, except a dulling of the screen just after sign-in, as though it is about to switch to a Screen-saver, then changes its mind and goes back to its normally bright screen. The dulling of the screen to an almost dark screen lasts approximately five seconds, this is on Version 9.04. Jaunty Jackalope. Sunday 21st June 20099 11.30am local tiime. Hugo shepherd

Not an xorg bug, refiling under linux. Can you have a look at https://help.ubuntu.com/community/DebuggingSystemCrash and provide the information requested, and any files as separate attachments? Thank you.

@Hugo: Your comment does not suggest that you are having the same problem as the original reporter, please file a new bug report for the dimming issue.

just catched this hung again....its maybe 30th...

i tried alt+sysrq+1 then alt+sysrq+t...and after reboot see nothing in kern log....kernel is hungs too

i think it is a file system bug..i have ext4.....this time it hunged when i downloaded 6 songs at the same time...past hungs was for example on mysql start, or eclipse close(saving resources window)

retif, When you try the Alt+SysRq+1 and t, does it dump anything to the screen? If it doesn't dump to kern.log but it shows something, can you write it down or take a photo of it somehow?
Also can you please run a FULL memory test, it's in the GRUB boot menu under memtest. It ill take 15-30 minutes. It may well be a RAM fault.
Thank you.

grub memory test is passed normally

I'm running Jaunty 9.04 32 bit, I too have tried the memory test, twice now, each ran for three iterations, my system just freezes, I have determined I had one bad ram stick and removed it, leaving me with 1GB but that ram passes the memory test and yet my system just freezes for no obvious reason.

Thank you for the update. Would you be able to provide a screenshot or
photo of the trace that appears when you follow the debugging system
crash instructions, as the system may not be sufficiently alive to log
anything in kern.log? Thank you.

I had the system lockups with a 32bit 9.04 install and now I have a fresh install of 9.10 64bit (server) with all the daily updates and I'm still experiencing lockups and sometimes kernel panics. I'm going to try to find or buy some other RAM to help determine if it's a RAM issue. Funny thing is that the computer had been running great for over a year until it started to lockup so much that I though an OS re-installation would fix it, alas it has not resolved the issue yet.

It definitely sounds like a hardware failure, that's not to say Ubuntu isn't at fault, but I would recommend thoroughly testing the RAM and/or hard drive, which may also be (sadly) failing.

Im having something like that, Im using ubutnu 9.04 and sometimes the system just freeze. All stops, but the mouse keeps working, but I cant open or close anything, is dificult to see any log file, because keyboard freezes too. This seems to be something on the kernel or soo, because in fedora 11 I have the same problem. Windows XP works fine. HD and memory are ok, I tested both.

Is anyone knows what to do or where to look for a log file to see what could bring this kind of problem I will be glad.

thanks a lot guys.

This machine is a HP laptop with a turion 64 with a ATI IXP.

I think I resolved my issues. I feel a bit stupid and I'm not sure how it happened as I'm not an overclocker nor do I ever condone overclocking. I took at look in my BIOS and somehow the RAM/memory timings and speed settings had changed. I changed the RAM timings to something more conservative like 5-5-5-12 and 1066. There was also a setting that was set to "Turbo" which I changed back to "normal" and so far so good.

If you're having spontaneous hang ups, lock-ups, crashes, kernel panics or just plain weirdness with your computer despite fresh OS installs then I suggest you take a look in your BIOS and tone things back a bit with the RAM settings and stop overclocking anything if you are.

Ferrazrafael - I'm not sure you'll have these settings in your BIOS since you have a laptop but it's worth a look. If you don't have the specific timings/speed settings then make your BIOS load the "Fail safe" settings and see if that doesn't help.

Perdignus.

Perdignus,

i think, that in my case, it isnt a problem.. in windows it works flawlesly.. and memtest works fine to..

what Im starting to wander is if is some kind of problem with the cpu frequency scaling.. because Im receiving this message in the system log analyser

"Clocksource tsc unstable (delta = -277649108 ns)"

I put the clocksource=acpi_pm in the grub menu.lst but this messages still there..

@Neil Munro
Can you check all your BIOS settings are also set to failsafe defaults, in case yours is also to do with RAM timings, etc. Also, can you test this in the latest daily build of Karmic 9.10, it should be reproducible with the Live CD. If it does crash, hopefully apport will kick in, and then it can be uploaded with appropriate debugging information, but I'm hoping that this was fixed in Karmic. Thank you.

@All other users
Please ensure that you are experiencing the same issue as the original reporter, as there may be several different root causes here, if you feel it is different, please open another bug report.

This issue is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!