I had the same stability issues when using x86_64 version of Hardy. This 
problem is not related to vmware-player since I don't use that program and 
still sees the same problem. 
I did notice that we do have the same moderboard chipset and are both using a 
quad core AMD Phenom CPU. I also have a nVidia card, but it is an older version 
compared to you.

The Ooops is always related to memory access that fails. I first though
that I had a bad memory module, but memtest reported all memory as good
and the fact that the system is stable with a 32-bit kernel suggest that
the memory is OK.

I would guess that the problem is either related to the CPU (unlikely
since that would affect very large number of users) or the motherboard
chipset. All my outputs are from 32-bit version of Hardy, I removed the
x86_64 installation since it was unusable on this system.

# cat /proc/cpuinfo 
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 2
model name      : AMD Phenom(tm) 9750 Quad-Core Processor
stepping        : 3
cpu MHz         : 2411.060
cache size      : 512 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc pni cx16 popcnt lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs ts ttp tm stc 
100mhzsteps hwpstate
bogomips        : 4827.35
clflush size    : 64

[and same info for 3 more cores]

I've attached the output from "sudo lspci -nvv"


** Attachment added: "lspci.txt"
   http://launchpadlibrarian.net/18285237/lspci.txt

-- 
[hardy] random kernel Oops with 2.6.24-16-generic x86_64 started after last 
hardy package update
https://bugs.launchpad.net/bugs/221223
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to