From: CaT <cat@zip.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.66-mm3: hang and crash
Date: Fri, 4 Apr 2003 13:14:02 +1000 [thread overview]
Message-ID: <20030404031402.GA457@zip.com.au> (raw)
In-Reply-To: <20030403183604.6a4cc385.akpm@digeo.com>
On Thu, Apr 03, 2003 at 06:36:04PM -0800, Andrew Morton wrote:
> > 2. After I booted, I logged into X, started up my mutts (6 of em) and
> > started moving the mouse cursor about. Laptop turned itself off.
>
> The first thing to do when a -mm kernel mysteriously explodes is to try just
> the Linus part. Could you please do that?
Done.
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.66/2.5.66-mm3/broken-out/linus.patch
>
> It is against 2.5.66.
I had to apply the framebuffer patch so that my kernel would not crash
for that reason (this was applied to the original mm3 aswell - forgot to
metnion). Also the percentile tmpfs was applied. Normal kernel works
fine with both patches.
Still, the linus.patch produced the same result. If you think it's
worthwhile I'll compile out the fa and perc patchesb but I didn't think
it significant due to them workign just fine with 2.5.66.
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
next prev parent reply other threads:[~2003-04-04 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 1:37 2.5.66-mm3: hang and crash CaT
2003-04-04 2:36 ` Andrew Morton
2003-04-04 3:14 ` CaT [this message]
2003-04-04 3:52 ` Andrew Morton
2003-04-05 0:30 ` CaT
2003-04-04 11:31 ` Felipe Alfaro Solana
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=20030404031402.GA457@zip.com.au \
--to=cat@zip.com.au \
--cc=akpm@digeo.com \
--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