public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Mark and Loretta Goldberg
	<goldber-sy4M0opG+ma2PmBBfd0Sh6xOck334EZe@public.gmane.org>
Cc: "acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Nforce2 crashes
Date: Fri, 17 Oct 2003 13:23:13 +0200	[thread overview]
Message-ID: <20031017112313.GC7738@elf.ucw.cz> (raw)
In-Reply-To: <200310170722.AAA71496-cEaiEdr7iMHEOYAad6Za0NHuzzzSOjJt@public.gmane.org>

Hi!

> I've got a FIC AU13, Athlon 2500+, 1 GB Dual Channel PC3200 DDR, 2.4.22 kernel.
> 
> If APIC support is compiled in, the machine crashes once or twice per day, solid lockup, hard reboot needed.
> If APIC support is not compiled in, it has been fine for weeks.

> If anyone is interested,  what can I send to troubleshoot the
> problem?

Well, patch to dmi_detect nforce2 and panic machine at boot if APIC is
enabled would be welcome. See arch/i386/kernel/dmi_scan.c.

									Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

      parent reply	other threads:[~2003-10-17 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  7:26 Nforce2 crashes Mark and Loretta Goldberg
     [not found] ` <200310170722.AAA71496-cEaiEdr7iMHEOYAad6Za0NHuzzzSOjJt@public.gmane.org>
2003-10-17 11:23   ` Pavel Machek [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=20031017112313.GC7738@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=goldber-sy4M0opG+ma2PmBBfd0Sh6xOck334EZe@public.gmane.org \
    /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