public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Tyler Riddle <triddle_1999@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel hangs approximitly every 3 days, some times during boot on version 2.4 and 2.6
Date: Thu, 01 Apr 2004 18:02:59 -0800	[thread overview]
Message-ID: <406CC9D3.9030604@mvista.com> (raw)
In-Reply-To: <20040401034824.99925.qmail@web41313.mail.yahoo.com>

Tyler Riddle wrote:
> Hello,
> 
> You can find a detailed bug report folowing the
> template specified in REPORTING-BUGS at
> http://foodmotron.homeunix.org/~tyler/bug-report.txt
> 
> In short, the kernel will hard lock on my machine
> about every 3 days. I have tried several of the latest
> versions of the 2.4 and 2.6 series kernels, 2.2 has
> not shown this problem. I have tried to remedy this
> problem by removing APIC support, IDE DMA and explicit
> support for my IDE chipset
> (VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235), none of
> which has helped any. On every lockup the IDE disk
> access light has been steady and usualy a steady tone
> is left playing out of my sound card.

I am going to take a stab in the dark here and question if it is the sound card 
or the cpu (i.e. in the box, speaker, etc.) that the sound is comming from.  If 
so, it could be that your cpus internal monitor has detected an alarm condition, 
such as voltage out of range, or, and most likely, over temp.  You might want to 
get your "sensors" set up so you can check from time to time.  Might even want 
to put together a script that writes to the system log when ever a sensor is in 
alarm condition.

And yes, linux stresses the box more than windoz, so it will over temp while 
windoz does not.

-g
> 
> I'm hoping someone here can help me figure out what is
> going on. This exact same hardware in the exact same
> configuration ran Windows 2000 for over a year with
> out issue. To verify the problem was localized to the
> linux kernel I also ran FreeBSD 5.2.1 for 3 weeks
> after the lockup problem existed under linux.
> 
> Thanks for your help,
> 
> Tyler Riddle
> 
> =====
> "There are only 10 types of people in this world: Those who understand binary and those who don't."
> 
> aim: TheMastaSpice
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway 
> http://promotions.yahoo.com/design_giveaway/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


      reply	other threads:[~2004-04-02  2:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  3:48 Kernel hangs approximitly every 3 days, some times during boot on version 2.4 and 2.6 Tyler Riddle
2004-04-02  2:02 ` George Anzinger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=406CC9D3.9030604@mvista.com \
    --to=george@mvista.com \
    --cc=ganzinger@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=triddle_1999@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox