linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: Paul Symons <PaulS@paradigmgeo.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: kernel oops 2.4.24
Date: Tue, 13 Jan 2004 18:59:48 +0000	[thread overview]
Message-ID: <20040113185948.GA17867@axis.demon.co.uk> (raw)
In-Reply-To: <798DD0DBF172864C8CC752175CF42BA326C8B2@pat.aberdeen.paradigmgeo.com>

On Tue, Jan 13, 2004 at 11:44:18AM -0000, Paul Symons wrote:
> I'm having a few problems with 2.4.24. I keep suffering oops's when
> performing intensive operations. 
> 
> Hardware: VIA EPIA 5000 / C3 processor

I've been extensively thrashing one of these recently.  I've compiled
several kernels for it, but all with the "CyrixIII" for VIA Cyrix III
or VIA C3 option.  This sets CONFIG_MCYRIXIII.

Have you tried memset86 on the hardware?

> I am trying to run Gentoo on this hardware, and have had problems from the
> start, with respect to compiling things like Gentoo. The hardware is a
> little bit of an oddity, because i read that it is classed as i686, yet it
> doesn't support the cmov opcode. All my compile optimisations have been at
> best i586 as a result.

I wonder if you are thinking of the Nehemiah (the C3 mark 2) rather
than the Samuel which is on that board.  As far as I'm aware its only
safe to use i386 code and that is what we've been using very
succesfully (with a Debian/stable installation).

> I'm not sure why ksymoops reports it as i686. I had originally tried running
> on 2.6.0, however I kept getting oops's with the via-rhine driver, so I
> thought I'd try with 2.4.24. The only difference with my config between
> 2.6.0 and 2.4.24 was that 2.6.0 was optimised for VIA-C3 processor type,
> while 2.4.24 was optimised for i586.

2.4.23 does have a C3 option.

However that said my attempts to get this board to run 2.4.23 have
failed because the IDE driver refuses to initialise - as if it doesn't
understand the PCI ID, eg under 2.4.19 I get this

VP_IDE: IDE controller on PCI bus 00 dev 89
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci00:11.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
hda: QUANTUM FIREBALLP LM20.5, ATA DISK drive

But under 2.4.23 - nothing!  The module loads from the initial ram
disk (I'm 100% sure of this because I've done it by hand from the
initial ram disk shell) but it prints nothing!

I haven't tried 2.4.24 - there didn't appear to be any appropriate
changes in the ChangeLog.

-- 
Nick Craig-Wood
ncw@axis.demon.co.uk

  reply	other threads:[~2004-01-13 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 11:44 kernel oops 2.4.24 Paul Symons
2004-01-13 18:59 ` Nick Craig-Wood [this message]
2004-01-13 19:13   ` David Rees
2004-01-14  8:23     ` Kernel oopses both 2.4.24 and 2.6.1 Roger Abrahamsson
2004-01-14  5:27   ` kernel oops 2.4.24 Dave Jones
2004-01-14  9:36 Paul Symons

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=20040113185948.GA17867@axis.demon.co.uk \
    --to=ncw1@axis.demon.co.uk \
    --cc=PaulS@paradigmgeo.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;
as well as URLs for NNTP newsgroup(s).