public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "kernel + gcc 4.1 = several problems" / "Oops in 2.6.19.1"
Date: Wed, 3 Jan 2007 21:20:00 +0100	[thread overview]
Message-ID: <20070103202000.GJ20714@stusta.de> (raw)
In-Reply-To: <459BCAD5.2020604@xs4all.nl>

On Wed, Jan 03, 2007 at 04:25:09PM +0100, Udo van den Heuvel wrote:
> Hello,
> 
> I just read about the subjects.
> I have a firewall which has some issues.
> First it was a VIA CL6000 (c3).
> Now it is a EK8000 (c3-2) with different power supply, RAM and board of
> course. Still I see strange things sometimes. Crashes, hangs, etc. Now
> and then. Not too often.
> 
> I have in .config:
> CONFIG_CC_OPTIMIZE_FOR_SIZE=y
> CONFIG_MVIAC3_2=y
> 
> Does this mean the issue applies to my own kernels?

It could be.
Or it could be something completely different.

If the same kernel compiled with gcc 3.4.6 works fine, you might run 
into one of the mysterious problems with gcc 4.1.

It could also be hardware problems (e.g. try running memtest86 for a 
longer time).

Does the machine hang completely, or is any useful information like e.g. 
an oops available?

> Udo

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2007-01-03 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03 15:25 "kernel + gcc 4.1 = several problems" / "Oops in 2.6.19.1" Udo van den Heuvel
2007-01-03 20:20 ` Adrian Bunk [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=20070103202000.GJ20714@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /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