Hardy hard lock-up...

[Shannon McMackin]

David Vincent wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Shannon McMackin wrote:
>> OK, I was using Hardy all the way through the beta cycle and never had 
>> this problem.  Now I have a fresh install of Hardy and I have this issue 
>> where X will seem to lock up completely though I can move the mouse. 
>> Now button clicks don't work, no key combos work, only the 1-finger 
>> salute recovers from this...
>>
>> Now, I've read about flash issues, so I un-installed Adobe flash and use 
>> some of the other flash tools like gnash. It still locks..
>>
>> I installed preload, so maybe that has something to do with it.  Anyone 
>> else using preload with out issues?
>>
>> This last lock-up, all that was running was FF3, Thunderbird and my VPN 
>> software.  Dmesg, messgaes and kern.log don't show anything useful other 
>> than the recovery from orphaned inodes...
> 
> what kernel are you running?  had you booted directly into that session
> or had you resumed from suspend/hibernate?  have you checked your RAM
> lately?
> 
> just some questions to get things going and get your mind percolating.
> 
> - -d
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFIT9cOfpRzWFIV0XMRAnQeAJ9NGv0xJm80Pi7mo3U/PPTDDA6mKQCeKGyv
> bMHsaMbdBimySYSnEg+GLQo=
> =GibE
> -----END PGP SIGNATURE-----
> 
I've been seeing this with 2.6.24-17-generic, 2.6.24-18-generic and 
2.6.24-19-generic, although my 19 now seems messed up because the 
compat-wireless update I tried to apply has unresolved symbols and won't 
load.

I did not see this on 2.6.24-16, but I was not there very long.

This does not happen on a spare drive running FC9, so I doubt it's RAM.

I did suspect some drive issues as while I was in beta usage I 
encountered some ATA error messages at boot time, but I think it was due 
to a messed up initrd image when I was playing with tuxonice.  I 
reinstalled with final release Hardy and did not see that error anymore.

I ran drive diags last night which indicated the controller and disk passed.

Upon this latest boot an e2fsck was run per normal boot count.

The only thing that I can think that I added was preload.  I have a 
co-worker with the same model laptop also running Hardy and I'm waiting 
to get in touch with him to verify what he has installed.