Ubuntu Hardy Freezes Randomly

[Travis "TeamColtra" McCrea]

My Dell Dimension E510 freezes up at random intervals (regardless of what application is open), and I only have use of my mouse, but it doesn't interact with anything (its like running your mouse over a picture).

I have already tried (ctr) Alt+ F2 AND + Backspace neither work.

The only option I have is to restart my computer via the power button. I have been running Ubuntu for the past 3 years on a Dual Boot but I finally made the switch over to Ubuntu FULLY and when I reinstalled Ubuntu... thats when this started happening.

"
Thank you for your interest in Ubuntu 8.04
         - the Hardy Heron - released in April 2008.
"

[goto (gotolaunchpad)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies I would look at: https://help.ubuntu.com/community/DebuggingSystemCrash Thanks in advance!

[Travis "TeamColtra" McCrea (teamcoltra)]

Linux Geeks-Paradox 2.6.24-22-generic #1 SMP Mon Nov 24 18:32:42 UTC 2008 i686 GNU/Linux

I could not seem to get the other two to work.

[goto (gotolaunchpad)]

If you enter the other two commands files will be created in the folder, where you are in. Probably your home folder. Look there if those files are there.

Have you a second machine with which you could ssh to the crashing one as described in "debugging system crash"?
Thanks.

[Travis "TeamColtra" McCrea (teamcoltra)]

I have generated these RIGHT after a crash.

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.24-22-generic (buildd@vernadsky) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon Nov 24 18:32:42 UTC 2008 (Ubuntu 2.6.24-22.45-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fe88c00 (usable)
[ 0.000000] BIOS-e820: 000000007fe88c00 - 000000007fe8ac00 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007fe8ac00 - 000000007fe8cc00 (ACPI data)
[ 0.000000] BIOS-e820: 000000007fe8cc00 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
[ 0.000000] BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] 1150MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000fe710
[ 0.000000] Entering add_active_range(0, 0, 523912) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 523912
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 523912
[ 0.000000] On node 0 totalpages: 523912
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2301 pages used for memmap
[ 0.000000] HighMem zone: 292235 pages, LIFO batch:31
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: RSDP signature @ 0xC00FEB00 checksum 0
[ 0.000000] ACPI: RSDP 000FEB00, 0024 (r2 DELL )
[ 0.000000] ACPI: XSDT 000FD25D, 005C (r1 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: FACP 000FD355, 00F4 (r3 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: DSDT FFFC74FC, 2D0E (r1 DELL dt_ex 1000 INTL 20050309)
[ 0.000000] ACPI: FACS 7FE88C00, 0040
[ 0.000000] ACPI: SSDT FFFCA32B, 00AC (r1 DELL st_ex 1000 INTL 20050309)
[ 0.000000] ACPI: APIC 000FD449, 0072 (r1 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: BOOT 000FD4BB, 0028 (r1 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: ASF! 000FD4E3, 0067 (r16 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: MCFG 000FD54A, 003E (r1 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: HPET 000FD588, 0038 (r1 DELL DM051 7 ASL 61)
[ 0.000000] ACPI: DMI detected: Dell Dimension 5150
[ 0.000000] ACP...

[Travis "TeamColtra" McCrea (teamcoltra)]

This issue is still affecting me, and it seems to be completly random. I can just be moving my mouse around and it will freeze.

I checked my system and its not over heating.

[Travis "TeamColtra" McCrea (teamcoltra)]

Another bug, that I don't know if they are related, but when I start some applications, its like they don't remember system settings... such as xchat not remembering what server I want to join upon opening, and that I don't want to open the server list.

Also Audacity runs "first run" every time I open it.

[Travis "TeamColtra" McCrea (teamcoltra)]

I have updated to .10 and still having the same issue

[gmurnane (gmurnane)]

Try running a memory testing program. I had similar random crashes, and Ubuntu's memory tester (in the grub menu accessible during boot up) returned errors.

[David Tombs (dgtombs)]

Awaiting reply from reporter.

[Pedro Villavicencio (pedro)]

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!.