public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gilles Espinasse <g.esp@free.fr>
To: "Marian Aldenhövel" <marian.aldenhoevel@mba-software.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building a kernel for SiS55-based system.
Date: Thu, 26 Jun 2008 11:16:07 +0200	[thread overview]
Message-ID: <1214471767.48635e574384b@imp.free.fr> (raw)
In-Reply-To: <4860959E.6020207@mba-software.de>

Selon Marian Aldenhövel <marian.aldenhoevel@mba-software.de>:

> Hi,
>
> I am trying to build a linux kernel for a small form-factor PC. I have so
> far failed to create a working kernel.
>
> Output of /cat/proc/cpuinfo as given by the hardware vendor:
>
>   > processor       : 0
>   > vendor_id       : SiS SiS SiS
>   > cpu family      : 5
>   > model           : 0
>   > model name      : ff/00
>   > stepping        : 5
>   > cpu MHz         : 200.008
>   > fdiv_bug        : no
>   > hlt_bug         : no
>   > f00f_bug        : no
>   > coma_bug        : no
>   > fpu             : yes
>   > fpu_exception   : yes
>   > cpuid level     : 1
>   > wp              : yes
>   > flags           : fpu tsc cx8 mmx
>   > bogomips        : 398.95
>
> I gather that is a SiS 55x System-on-a-chip.
>
> I am using T2[1] as build-system. It (currently) tries to build the kernel
> from 2.6.25.7 sources. When booting the kernel it built the system stops
> after:
>
>    Decompressing Linux... done.
>    Booting the kernel.
>
> At the bottom of the screen it says:
>
>    BUG: Int6: CR2 00000000
>
> And nothing else.
>
Int6 mean invalid opcode

I find same error messages
on opensuse beta with linux-2.6.24 and real hardware
http://forums.opensuse.org/archives/sf-archives/opensuse-beta/347272-updated-last-night-kernel-bug-now.html

on debian kernel under MS VirtualPC
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463606


What version of gcc,binutils?

Could you try with distrib images to know if it could be related to your
compilation system or use a distrib kernel config to test on your compilation
system?

Instead of CONFIG_M386=y, you may try to select M486 or M586
( maybe later with tsc and mmx as cpuinfo flags line report it is supported).


Gilles

  reply	other threads:[~2008-06-26  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  6:35 Building a kernel for SiS55-based system Marian Aldenhövel
2008-06-26  9:16 ` Gilles Espinasse [this message]
2008-07-06  8:49   ` Marian Aldenhövel
2008-07-06 10:31     ` Gilles Espinasse
2008-07-11 15:43       ` Building a kernel for SiS55-based system. No, wait! It's a Vortex86SX Marian Aldenhövel
2008-07-11 15:31         ` Alan Cox
2008-07-11 15:35         ` Alan Cox

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=1214471767.48635e574384b@imp.free.fr \
    --to=g.esp@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marian.aldenhoevel@mba-software.de \
    /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