From: Lee Revell <rlrevell@joe-job.com>
To: Valdis.Kletnieks@vt.edu
Cc: Mathieu Segaud <matt@minas-morgul.org>,
sboyce@blueyonder.co.uk,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.9-rc4-mm1 Oops [2]
Date: Tue, 12 Oct 2004 15:01:46 -0400 [thread overview]
Message-ID: <1097607706.1553.79.camel@krustophenia.net> (raw)
In-Reply-To: <200410121607.i9CG7PsQ001076@turing-police.cc.vt.edu>
On Tue, 2004-10-12 at 12:07, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 12 Oct 2004 11:39:11 +0200, Mathieu Segaud said:
> > Sid Boyce <sboyce@blueyonder.co.uk> disait dernièrement que :
> >
> > > This one on attempting to start firefox.
> > > Regards
> > > Sid.
> >
> > about the 2 reports you made about oopses, try this
> > cd /path/to/your/kernel/source
> > wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc4/
> 2.6.9-rc4-mm1/nroken-out/optimize-profile-path-slightly.patch
> > patch -R -p1 -i optimize-profile-path-slightly.patch
>
> I started seeing the same problem on -rc4-mm1, and couldn't figure out why
> I didn't see it on -rc3-mm3. Finally figured out that it was because the
> -rc3-mm3 had a -VP patch on it, and the -rc4-mm1 didn't (because of the
> UP build problems in -T5). Ingo's patch also reverts that patch, so I got
> the fix 'free of charge'....
I assumed that Ingo added this to the VP patch intentionally so he
didn't get a zillion bug reports.
Lee
next prev parent reply other threads:[~2004-10-12 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 8:25 2.6.9-rc4-mm1 Oops [2] Sid Boyce
2004-10-12 9:39 ` Mathieu Segaud
2004-10-12 10:51 ` Kalin KOZHUHAROV
2004-10-12 16:07 ` Valdis.Kletnieks
2004-10-12 19:01 ` Lee Revell [this message]
2004-10-12 19:14 ` Ingo Molnar
2004-10-13 0:04 ` Sid Boyce
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=1097607706.1553.79.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@minas-morgul.org \
--cc=mingo@elte.hu \
--cc=sboyce@blueyonder.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.