Before leaving the thread, I wanted to report my resolution in hopes it
might help someone who views this in the future.
I am using an Intel D945GCLF2 motherboard, equipped with an Intel N330
Atom dual-core chip. The build included a DDR2 800 2GB chip with
6-6-6-18 timings that should have
I swapped out my 6-6-6-18 memory for a 4-4-4-`1 memory and my freezing
seems to ahve gone away. Of note is that my BIOS is supposed to offer
667MHz memory support, but it is not shown as a selection int he BIOS
config. I have been running the system around-the-clock with
Thunderbird running for
the next time, could you see if the BIOS reports the memory
configuration? My timings are 6-6-6-18 but 5-5-5-15 is recommended. I am
changing the memory this week when a new stick arrives.
On 06/15/2010 03:48 PM, phlip lawrence wrote:
Tech2010
There are no GPU nor drm errors in any of the log
I seem to still have the freeze. This is an Atom2 motherboard. The BIOS
suggests using 2GB DDR2 memory with 5-5-5-15 (667MHz) timings, but the
board is equipped with a 2GB 6-6-6-18 (800MHz). Because of the sudden
death of the freeze, I started to wonder about memory. So, I wrote a
little
Can you tell me if your system has an error in the logs for a GPU
lockup? Or another drm error?
Also, does your motherboard use the CPU to manage workload for the GPU?
Anything like this in there?
Jun 13 11:39:28 ATOM2 kernel: [30231.584518]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck
I installed an Intel Ethernet (PCI) adapter, disabled the on-board
ethernet adapter, and the problem is gone. My hardware is the Intel
D945GCLF2 Motherboard, and I've seen postings as old as 2008 with
comments on the low-end NIC causing issues from day-one. I hope you all
are as fortunate to get
I wonder if many folks are using NFS 3 here.
I do have the error about locks before the freezes. (failed to register lockdv1
RPC)
But I ran a remote ssh all night tailing messages and nothing, including
no freeze.
--
Ubuntu 10.04 random freezes
https://bugs.launchpad.net/bugs/585765
You
This seems to be the last logged message before freeze for me:
rsyslogd: [origin software=rsyslogd swVersion=4.2.0 x-pid=624
x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'.
After this message, rsh connection is closed and system is frozen.
In the latest case, there were
The usual suspects, but now I suspect there is no real message
associated with the root cause:
Jun 9 18:45:15 ATOM2 kernel: [ 37.675908] svc: failed to register lockdv1
RPC service (errno 97).
Jun 9 18:49:37 ATOM2 kernel: [ 299.988020] Machine check events logged
Jun 9 18:52:27 ATOM2
For my system, last night's kernel reintroduced the bug. The kernel
before did not have it.
Ubuntu 10.04 LTS, kernel 2.6.32-22-generic freezes.
Ubuntu 10.04 LTS, kernel 2.6.32-21-generic does not.
Your mileage may vary.
With -21 I was able to go five days without a freeze.
With -22, I have
Here's what happens when the system does NOT freeze but the keyboard
doesn't work inside any applications:
Jun 5 17:23:13 ATOM2 kernel: [15972.360061] hub 2-0:1.0: port 1 disabled by
hub (EMI?), re-enabling...
Jun 5 17:23:13 ATOM2 kernel: [15972.360073] usb 2-1: USB disconnect, address 2
Jun
It is probably not definitive but I have not had a freeze since I
removed VirtualBox OSE from the system four days ago. I have
intentionally left Thunderbird running, randomly checking remote email
accounts. I'm am encouraged but not yet convinced.
--
Ubuntu 10.04 random freezes
I believe I see both of these conditions on the Intel dual-core Atom
N330 motherboard.
I have a monitor with both DVI and VGA inputs. The board in question
uses the VGA input. Fairly frequently, when I switch from DVI use back
to VGA use, the screensaver is active. But the system is frozen.
13 matches
Mail list logo
