public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lockup with 2.4.9-ac10 on Athlon
Date: Fri, 21 Sep 2001 15:39:44 +0100	[thread overview]
Message-ID: <32748.1001083184@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010921101144.28645B-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1010921101144.28645B-100000@gatekeeper.tmr.com>


davidsen@tmr.com said:
> > Strange - mine works. Either with APM and 'apm=power-off' on the
> > command line, or with ACPI and a hack to work around the incompetence of
> > Abit's BIOS engineers.

> Is this something Linux could recognize and patch, like the Athlon
> problem with the VIA chipset? 

'Could', yes. 'Should', probably not. It's bad enough that we have to run 
binary-only code from people with this little clue, without having to apply 
patches to it as well.

This is the patch I was using at the time. It won't apply now.

Index: drivers/acpi/namespace/nsalloc.c
===================================================================
RCS file: /inst/cvs/linux/drivers/acpi/namespace/Attic/nsalloc.c,v
retrieving revision 1.1.2.5
diff -u -r1.1.2.5 nsalloc.c
--- drivers/acpi/namespace/nsalloc.c    2001/06/21 09:40:16     1.1.2.5
+++ drivers/acpi/namespace/nsalloc.c    2001/08/11 15:58:51
@@ -60,6 +60,10 @@
        INCREMENT_NAME_TABLE_METRICS (sizeof (ACPI_NAMESPACE_NODE));
 
        node->data_type      = ACPI_DESC_TYPE_NAMED;
+       if (acpi_name == 0x5f555043) {
+               printk("Fixing up object 'CPU_' to name 'CPU0'\n");
+               acpi_name = 0x30555043;
+       }
        node->name           = acpi_name;
        node->reference_count = 1;
 


--
dwmw2



      reply	other threads:[~2001-09-21 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 18:01 Lockup with 2.4.9-ac10 on Athlon Ignacio Vazquez-Abrams
2001-09-09 22:09 ` Ignacio Vazquez-Abrams
2001-09-10  0:24   ` Ignacio Vazquez-Abrams
2001-09-10  0:49     ` Kurt Garloff
2001-09-10  4:16     ` Ignacio Vazquez-Abrams
2001-09-20 22:08       ` bill davidsen
2001-09-20 22:32         ` Ignacio Vazquez-Abrams
2001-09-21 11:42         ` David Woodhouse
2001-09-21 14:17           ` Bill Davidsen
2001-09-21 14:39             ` David Woodhouse [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=32748.1001083184@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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