Re: diagnosing hard-locks

2006-07-10 Thread Andrew Sackville-West
On Mon, Jul 10, 2006 at 10:04:57AM +0200, Dominique Dumont wrote: > Andrew Sackville-West <[EMAIL PROTECTED]> writes: > > > If transcode jobs run well, I think your CPU is ok, even though i > think 56C is quite hot (my barton XP 3200 is about 42 C now, 48C when > transcoding). huh. well, I'll l

Re: diagnosing hard-locks

2006-07-10 Thread Dominique Dumont
Andrew Sackville-West <[EMAIL PROTECTED]> writes: > yeah, another good idea. unfortunately, that's a no go either. I'm > running at a pretty steady 132 F/ 56 C right now with it climbing to > about 140F, but no more when I'm pushing it. Also, it seems more > common when I'm NOT working. Also, does

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Willie Wonka
Andrew Sackville-West wrote: > On Sat, Jul 08, 2006 at 12:48:44PM -0700, Willie Wonka wrote: > > I have NOT yet *chosen* memtest86+ from my GRUB menu, but it's there now, and I > > will try to boot into it during next reboot ;-) > > cool, I;m curious to see if others get the same results as I.

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Andrew Sackville-West
On Sat, Jul 08, 2006 at 12:48:44PM -0700, Willie Wonka wrote: > > > > > > > I googled the memtest issue and found one good hit that said you have > > to burn the img directly to a floppy. I've done that with dd and it > > works like a charm, boots right into memtest. It must be some grub > > rel

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Mumia W.
Willie Wonka wrote: [...] Whoops!! I forgot to add one VERY IMPORTANT point when running *update-grub* Remember to Copy down ANY/ALL Kernel and Initrd CUSTOM Boot settings!! [...] That's not a bad idea, but it's not necessary either. From /boot/grub/menu.lst: ## ## Start Default Options ## #

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Willie Wonka
Andrew Sackville-West wrote: > On Fri, Jul 07, 2006 at 09:22:59PM -0700, Willie Wonka wrote: > > ACPI hmm.. Let's see output of 'dmesg | grep ACPI' > [EMAIL PROTECTED]:~$ dmesg | grep ACPI > BIOS-e820: 0dfec000 - 0dfef000 (ACPI data) > BIOS-e820: 0dfff000 - 0e000

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Willie Wonka
Andrew Sackville-West wrote: > On Sat, Jul 08, 2006 at 02:02:42AM -0700, Willie Wonka wrote: > > > > ~$ sudo update-grub > > Searching for GRUB installation directory ... found: /boot/grub . > > Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . > > Searching for splash i

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Andrew Sackville-West
On Sat, Jul 08, 2006 at 02:02:42AM -0700, Willie Wonka wrote: > > ~$ sudo update-grub > Searching for GRUB installation directory ... found: /boot/grub . > Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . > Searching for splash image... none found, skipping... > Found ke

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Andrew Sackville-West
On Fri, Jul 07, 2006 at 09:22:59PM -0700, Willie Wonka wrote: [... stuff about cron jobs ...] definitely this is not my issue as it happens at any time of day. Also, this is truly a hard lock -- no disk activity, no response of any kind from any stimulus I can come up with. In fact, if the machine

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Willie Wonka
Willie Wonka wrote: > Back to you and Memtest86; > I too have used the Knoppix CD and type this at the prompt; > Boot: memtest86 > > Just did a bit of searching my local HD, and it turns out I hadn't yet > installed memtest86+ this time around - so I just recently installed it, since > I want to

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-08 Thread Willie Wonka
Willie Wonka wrote: > Couple of thoughts; > > * I notice the "nobody" account/group(?) start thrashing late at night, when > the monitor (only) has been sleeping for a little, which translates into me not > using the system and it's resources at that time (idle). I ran 'top' when I > heard this g

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Willie Wonka
Andrew Sackville-West wrote: > On Fri, Jul 07, 2006 at 11:08:00AM +0200, Dominique Dumont wrote: > > Andrew Sackville-West <[EMAIL PROTECTED]> writes: > > > > > now on to finding the source of my hard locks. ugh./ > > > > Be sure to check the temperature of your CPU. (been there) > > yeah, ano

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread hendrik
On Fri, Jul 07, 2006 at 11:11:39AM -0700, Andrew Sackville-West wrote: > On Fri, Jul 07, 2006 at 01:36:52PM -0400, Michael Marsh wrote: > > > > I actually had a suspiciously similar problem recently. A couple of > > times, everything just froze. The power button was the only thing > > that would

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Andrew Sackville-West
On Fri, Jul 07, 2006 at 04:53:16PM -0400, [EMAIL PROTECTED] wrote: > On Fri, Jul 07, 2006 at 11:11:39AM -0700, Andrew Sackville-West wrote: > > On Fri, Jul 07, 2006 at 01:36:52PM -0400, Michael Marsh wrote: > > > > > > I actually had a suspiciously similar problem recently. A couple of > > > time

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Andrew Sackville-West
On Fri, Jul 07, 2006 at 02:46:08PM -0400, Michael Marsh wrote: > On 7/7/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > >On Fri, Jul 07, 2006 at 02:24:12PM -0400, Michael Marsh wrote: > >> I'm *always* swapping on my laptop (which sounds really bad out of > >> context), since my 256MB of RAM

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Michael Marsh
On 7/7/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: On Fri, Jul 07, 2006 at 02:24:12PM -0400, Michael Marsh wrote: > I'm *always* swapping on my laptop (which sounds really bad out of > context), since my 256MB of RAM is taken up almost entirely by firefox > and thunderbird. And that's b

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Andrew Sackville-West
On Fri, Jul 07, 2006 at 02:24:12PM -0400, Michael Marsh wrote: > On 7/7/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > >On Fri, Jul 07, 2006 at 01:36:52PM -0400, Michael Marsh wrote: > >> I actually had a suspiciously similar problem recently. A couple of > >> times, everything just froze.

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Michael Marsh
On 7/7/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: On Fri, Jul 07, 2006 at 01:36:52PM -0400, Michael Marsh wrote: > I actually had a suspiciously similar problem recently. A couple of > times, everything just froze. The power button was the only thing > that would respond. memtest86+

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Andrew Sackville-West
On Fri, Jul 07, 2006 at 01:36:52PM -0400, Michael Marsh wrote: > On 7/7/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > >These locks are particularly frustrating as they leave no trace in the > >logs. the logs just stop until they come up from the reboot. I've seen > >it happen while I'm wor

Re: diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Michael Marsh
On 7/7/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: These locks are particularly frustrating as they leave no trace in the logs. the logs just stop until they come up from the reboot. I've seen it happen while I'm working maybe two or three times... just lock right up and be totally gone.

diagnosing hard-locks [was memtest+ won't load]

2006-07-07 Thread Andrew Sackville-West
On Fri, Jul 07, 2006 at 11:08:00AM +0200, Dominique Dumont wrote: > Andrew Sackville-West <[EMAIL PROTECTED]> writes: > > > now on to finding the source of my hard locks. ugh./ > > Be sure to check the temperature of your CPU. (been there) yeah, another good idea. unfortunately, that's a no go