Well, took everything apart today and put it all back together--we'll
see what happens.

Has anybody ever seen what I've described with the NumLock light?
Basically, when it's locked up, the NumLock light will light up when any
key is pressed, and then go back off when everything is released. It
would seem to me that the kernel would still have to be alive and
kicking in that case--any way to make it spit out a core dump when that
happens?

Thanks again!
Mike

On Mon, Oct 18, 2010 at 08:51:04PM -0700, Derek Simkowiak wrote:
>     The strange blinkenlights, plus recent case swap, make it sound
> like a hardware problem.
> 
>     Check all cables, reseat all cards, check for cracks in the
> mobo, check the bus mountings (esp. that USB with the intermittent
> power loss).  Check that the new case has sufficient cooling and
> that all the fans are plugged in and running (maybe your system is
> overheating in the new box).
> 
> 
> On 10/18/2010 08:43 PM, Mike Stunes wrote:
> >Hi all,
> >
> >I'm having some issues with random hard lockups on my Arch Linux box,
> >2.6.35 kernel. Sometimes random sound will start spewing out of the
> >speakers, sometimes my USB mouse/keyboard will completely lose power,
> >sometimes pressing a key on the keyboard will make NumLock light up as
> >long as the key is pressed. No blinking lights on the keyboard or
> >anything like that though.
> >
> >I thought it might have been MythTV (Hauppauge HVR-1800), but I've
> >disabled it, no luck.
> >
> >Also thought it might have been that I recently transplanted my computer
> >into a new case (don't think this happened at all with the old one). I
> >scratched up the motherboard a bit trying to get one of the mounting
> >screws out, but it seems that everything in the vicinity of the screw
> >hole is just a giant ground pad--can't imagine how scratching that a bit
> >would cause any problems.
> >
> >Motherboard is (I think) a Gigabyte GA-P55A-UD3; proc is a Core i7-860.
> >
> >I'll start running memtest86+ soon and see if anything interesting comes
> >up.
> >
> >Does anybody know what might be wrong, or how I can get some more useful
> >information?
> >
> >Thanks much!
> >
> >Mike
> 

Reply via email to