![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On 08/22/2010 09:39 AM, edwardp-mh2Nk+tgbQM at public.gmane.org wrote: > Jerry Feldman wrote: > > =20 >> This looks like a hardware issue. In the past, when I has a lockup, I >> would try to get into the system via ssh. First, were you able to ping= >> the system from another computer. Secondly, if you were able to ping i= t, >> could you connect to it via ssh (if sshd enabled)? >> =20 >> =20 > This morning, it booted up displaying a bunch of console messages, then= =20 > froze. Reviewed BIOS settings - made a change, rebooted, it came up=20 > fine. I did not try to ping it from another computer. > > The memory timing settings for each DIMM were set to Turbo, these were = > changed this to Normal. Medium and Fast are the other settings. > > =20 Run a memory diagnostic. Also check the dmesg results. --=20 Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846