From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Deon George <kernel@wurley.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: please help - kernel OOPS
Date: 16 Jul 2003 16:18:54 +0100 [thread overview]
Message-ID: <1058368734.6633.21.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030716120856.M31641@wurley.net>
On Mer, 2003-07-16 at 13:08, Deon George wrote:
> I have been trying some mini-ITX v8000 systems and can get a kernel oops quite
> easily - most times it is to do with making file systems (reiserfs or ext2/3) or
> copying via the network (using rsync). Sometimes it happens when the box is
> booting, and other times it has gone for serveral days before it happened.
I've got a set of EPIA boxes running these kernels - reliably. I would
suggest checking the RAM you used is up to spec first - I had a real
pain of a time with EPIA stuff until I used decent RAM. The stuff that
gave me problems worked fine on some other boards but only at 100Mhz bus
speed on the EPIA.
> I have captured two oops - one when I used mke2fs and one for mkreiserfs (since it
> oops quite frequently when I make a file system). Does this mean anything to
> anybody?
Are you within power budget for your system if its a tiny little PSU
brick ?
next prev parent reply other threads:[~2003-07-16 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 12:08 please help - kernel OOPS Deon George
2003-07-16 15:18 ` Alan Cox [this message]
[not found] ` <20030716223431.M85416@wurley.net>
[not found] ` <1058395864.7678.5.camel@dhcp22.swansea.linux.org.uk>
2003-07-18 0:38 ` Deon George
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=1058368734.6633.21.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=kernel@wurley.net \
--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).