From: Tony Lill <ajlill@ajlc.waterloo.on.ca>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [Bugme-new] [Bug 15214] New: Oops at __rmqueue+0x51/0x2b3
Date: Sun, 7 Feb 2010 13:34:58 -0500 [thread overview]
Message-ID: <201002071335.03984.ajlill@ajlc.waterloo.on.ca> (raw)
In-Reply-To: <20100205112000.GD20412@csn.ul.ie>
[-- Attachment #1: Type: Text/Plain, Size: 1506 bytes --]
On Friday 05 February 2010 06:20:00 Mel Gorman wrote:
> On Wed, Feb 03, 2010 at 02:39:21PM -0800, Andrew Morton wrote:
> > > gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
>
> This is a bit of a reach, but how confident are you that this version of
> gcc is building kernels correctly?
>
> There are a few disconnected reports of kernel problems with this
> particular version of gcc although none that I can connect with this
> problem or on x86 for that matter. One example is
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536354
>
> which reported problems building kernels on the s390 with that compiler.
> Moving to 4.2 helped them and it *should* have been fixed according to
> this bug
>
> http://bugzilla.kernel.org/show_bug.cgi?id=13012
>
> It might be a red herring, but just to be sure, would you mind trying
> gcc 4.2 or 4.3 just to be sure please?
Well, it was producing working kernels up until 2.6.30, but I recompiled with
gcc (Debian 4.3.2-1.1) 4.3.2
and the box has been running nearly 48 hour without incident. My previous
record was 2. So I guess we can put this down to a new compiler bug.
I probably should have checked this before reporting a bug. Mea culpa
--
Tony Lill, Tony.Lill@AJLC.Waterloo.ON.CA
President, A. J. Lill Consultants (519) 650 0660
539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461
--------------- http://www.ajlc.waterloo.on.ca/ ----------------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-02-07 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15214-10286@http.bugzilla.kernel.org/>
2010-02-03 22:39 ` Andrew Morton
2010-02-05 11:20 ` Mel Gorman
2010-02-07 18:34 ` Tony Lill [this message]
2010-02-08 10:10 ` Mel Gorman
2010-02-08 19:18 ` Andrew Morton
2010-02-09 14:45 ` Mel Gorman
[not found] ` <201002101217.34131.ajlill@ajlc.waterloo.on.ca>
2010-02-11 18:20 ` Mel Gorman
2010-02-11 18:49 ` Linus Torvalds
2010-02-12 12:17 ` Mel Gorman
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=201002071335.03984.ajlill@ajlc.waterloo.on.ca \
--to=ajlill@ajlc.waterloo.on.ca \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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