public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael C. de Almeida" <almeidaraf@gmail.com>
To: Samuel Sieb <samuel@sieb.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel won't boot on a Cyrix MediaGXm (Geode )
Date: Mon, 21 Jul 2008 03:36:33 -0300	[thread overview]
Message-ID: <48842E71.9070503@gmail.com> (raw)
In-Reply-To: <48841A92.4020301@sieb.net>

Samuel Sieb wrote:
> I have a computer here with a CPU that the BIOS identifies as:
> Cyrix MediaGXm/Cx5530 Unicorn Revision 1.19.3B
> 
> kernel 2.6.14 identifies it as:
> vendor_id    : Geode by NSC
> cpu family    : 5
> model        : 9
> model name    : Geode(TM) Integrated Processor by National Semi
> stepping    : 1
> 
> I can't boot any kernel later than 2.6.22 on it.  Anything later either
> hangs or gives random kernel panics while booting.  I tracked down the
> problem to a specific commit:
> 
> commit f25f64ed5bd3c2932493681bdfdb483ea707da0a
> Author: Juergen Beisert <juergen@kreuzholzen.de>
> Date:   Sun Jul 22 11:12:38 2007 +0200
> 
>     x86: Replace NSC/Cyrix specific chipset access macros by inlined
> functions.
> 
> Reversing the patch (compensating for kernel changes) let me boot a
> 2.6.25 kernel.  I realize the patch is supposed to fix something that
> didn't work right, but I didn't have a problem before and I do now. :-)
> -- 
> 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/

I couldn't figure out what the problem was, but shouldn't ccr3 be
declared as u8 in the following file? After all, that's what setCx86
expects. I realise that it being u32 will do no harm here, but I thought
I should point it out.

diff --git a/arch/x86/kernel/cpu/mtrr/cyrix.c
b/arch/x86/kernel/cpu/mtrr/cyrix.c
index ff14c32..e7d9f7e 100644
--- a/arch/x86/kernel/cpu/mtrr/cyrix.c
+++ b/arch/x86/kernel/cpu/mtrr/cyrix.c
@@ -123,7 +123,7 @@ cyrix_get_free_region(unsigned long base, unsigned
long size, int replace_reg)
 }

 static u32 cr4 = 0;
-static u32 ccr3;
+static u8 ccr3;

 static void prepare_set(void)
 {

  parent reply	other threads:[~2008-07-21  6:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  5:11 kernel won't boot on a Cyrix MediaGXm (Geode ) Samuel Sieb
2008-07-21  6:28 ` Juergen Beisert
2008-07-22  5:16   ` Samuel Sieb
2008-07-22  8:08     ` Juergen Beisert
2008-07-23  7:13       ` Samuel Sieb
2008-07-21  6:36 ` Rafael C. de Almeida [this message]
2008-07-21 11:47   ` Ingo Molnar
2008-07-22  5:10     ` Samuel Sieb
2008-07-22 10:24       ` Ingo Molnar
2008-07-22 10:51         ` Juergen Beisert
2008-07-23  7:18           ` Samuel Sieb
2008-07-28 15:32             ` Ingo Molnar
2008-07-28 17:58               ` Samuel Sieb
2008-07-29  9:18                 ` Ingo Molnar
2008-07-29  8:15               ` Juergen Beisert
2008-08-07  5:06               ` Samuel Sieb
2008-08-20  9:32                 ` Ingo Molnar
2008-08-20  9:44                   ` Juergen Beisert
2008-08-20 10:45                     ` Ingo Molnar
2008-08-20 11:03                       ` Juergen Beisert
2008-08-20 11:20                         ` Ingo Molnar

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=48842E71.9070503@gmail.com \
    --to=almeidaraf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel@sieb.net \
    /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