New 8.04, same problem

[NoOp]

On 09/12/2008 08:41 AM, elmo wrote:
> Here's a copy of my computer:
> 
> 
>> elmo-desktop
>>    description: Desktop Computer
>>    vendor: Lan Plus
>>    width: 32 bits
>>    capabilities: smbios-2.2 dmi-2.2 smp
>>    configuration: boot=normal chassis=desktop
>>  *-core
>>       description: Motherboard
>>       product: SiS-650
>>       physical id: 0
>>     *-firmware
>>          description: BIOS
>>          vendor: Phoenix Technologies, LTD
>>          physical id: 0
>>          version: 6.00 PG (01/09/2004)
>>          size: 128KiB
>>          capacity: 192KiB
>>          capabilities: isa pci pnp apm upgrade shadowing escd cdboot 
>> bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 
>> int13floppy2880 int5printscreen int9keyboard int14serial int17printer 
>> int10video acpi usb agp ls120boot zipboot
>>     *-cpu
>>          description: CPU
>>          product: Intel(R) Pentium(R) 4 CPU 2.50GHz
>>          vendor: Intel Corp.
>>          physical id: 5
>>          bus info: cpu at 0
>>          version: 15.2.9
>>          slot: Socket 478
>>          size: 2500MHz
>>          width: 32 bits
>>          clock: 100MHz
>>          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 sep 
>> mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up 
>> pebs bts sync_rdtsc cid xtpr
>>          configuration: id=0
>>        *-cache:0
>>             description: L1 cache
>>             physical id: b
>>             slot: Internal Cache
>>             size: 8KiB
>>             capacity: 20KiB
>>             capabilities: synchronous internal write-back
>>        *-cache:1
>>             description: L2 cache
>>             physical id: c
>>             slot: External Cache
>>             size: 512KiB
>>             capacity: 512KiB
>>             capabilities: synchronous external write-back
>>     *-memory
>>          description: System Memory
>>          physical id: 1c
>>          slot: System board or motherboard
>>          size: 512MiB
>>        *-bank:0
>>             description: DIMM [empty]
>>             physical id: 0
>>             slot: A0
>>        *-bank:1
>>             description: DIMM SDRAM Synchronous
>>             physical id: 1
>>             slot: A1
>>             size: 512MiB
>>             width: 64 bits

Thanks for that. Can you also tell us what brand of computer it is? (Lan
 Plus/Northgate is no longer in business it seems).

One thing I note is that your memory is in slot A1 vs A0; most
motherboards recommend the first memory module be installed in A0. That
may, or may not have anything to do with the problem, but it's worth
checking and also running the memory test at the grub boot just in case.

Looking through launchpad:
<https://bugs.launchpad.net/bugs/+bugs?field.searchtext=hardy+freeze&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=&start=0>
there are 337 reports regarding 'hardy freeze'. A random pick of a few:
https://bugs.launchpad.net/ubuntu/+bug/267836
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269248
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/239021
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/253071
etc., etc., seem to indicate that many users report working fine in
Gutsy, but freeze in Hardy. None of the reports appear to point to any
one thing that causes the problems.

I reckon that you can boot into Gutsy and spend the weekend looking
through the reports to see if you spot some suggestions/resolutions, but
I'd first try the memory test and then let's see if we can get your
system to actually provide some feedback when it does lock up. In order
to do the latter, you'll need to use the "magic SysRq key":

https://help.ubuntu.com/community/DebuggingSystemCrash
<quote>
When the crash occurs, press Alt+SysRq+1 (one, not L) followed by
Alt+SysRq+t. If using a text console, you should see a trace dumped to
the screen. If the system is sufficiently alive, it will also be logged
to /var/log/kern.log and visible in the output from dmesg. This
information shows where the crash occurred, and should be included in
any problem reports. If the output is not saved in any file, or the
system is so bad off that you cannot retrieve it, you can either take a
digital photo, or hand write the results. Almost all of the output is
important (so please don't copy the one line you think is important,
because context means everything).
</quote>

The SysRq key is the Print Scrn/SysRq key generally located up next to
the Scroll Lock key. Added information is located here:
http://lxr.linux.no/linux/Documentation/sysrq.txt

Note: the above may not work when your system freezes, but it's worth a
try as sometimes when things look totally frozen the Alt+SysRq+(1/t)
will work. If it does then we're one step further in finding the actual
problem. It it doesn't, then no harm done in trying.