From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.4+ dcache BUG.
Date: Mon, 21 May 2012 22:08:25 -0400 [thread overview]
Message-ID: <20120522020825.GA22961@redhat.com> (raw)
In-Reply-To: <CA+55aFwimihFb=JTFMraAhYFSwR6bBt_Pmwfx0wLybUDq1JQ0w@mail.gmail.com>
On Mon, May 21, 2012 at 06:51:51PM -0700, Linus Torvalds wrote:
> On Mon, May 21, 2012 at 6:11 PM, Dave Jones <davej@redhat.com> wrote:
> > Just hit this. Probably related to todays dcache changes ?
>
> Almost certainly. Except:
>
> > I'm not sure why, but the dcache.c line numbers don't match up..
> > This kernel was v3.3-rc7-14528-g29db10d which looked like..
>
> You seem to not have fetched any tags lately (so it says "3.3-rc7 +
> 14528 commits" instead of something more relevant), and I can't make
> sense of that SHA1 either (29db10d) either.
>
> You probably have other changes in your tree as well, explaining the
> SHA1 that I don't recognize?
ah, yeah. Mostly just stuff like removing noisy printk's that I get
tired of seeing when I run trinity.
> What was the load that triggered this? Just a regular kernel compile?
kernel build doing make -j 64 on a 8 way machine. (quad core with ht)
(It has a really fast ssd, so it can really churn through builds quickly).
> I see the "comm: cc1" there, and I'm a bit surprised, since I ran
> those patches here locally a *lot*. Is this perhaps some low-memory
> scenario?
hmm, that's a possibility. Machine has 4GB, but with all those gcc/ld's flying around,
maybe when it gets to a big link section..
Dave
prev parent reply other threads:[~2012-05-22 2:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 1:11 3.4+ dcache BUG Dave Jones
2012-05-22 1:39 ` Dave Jones
2012-05-22 1:58 ` Linus Torvalds
2012-05-22 2:14 ` Linus Torvalds
2012-05-22 2:36 ` Dave Jones
2012-05-22 1:51 ` Linus Torvalds
2012-05-22 2:08 ` Dave Jones [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=20120522020825.GA22961@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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