From: Larry McVoy <lm@bitmover.com>
To: Michel D?nzer <michel@daenzer.net>
Cc: Larry McVoy <lm@bitmover.com>, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6.0-test2-bk2 (linus' tree) -- arch/ppc/platforms/pmac_cpufreq.c:219: undefined reference to `cpufreq_frequency_table_verify'
Date: Mon, 4 Aug 2003 08:41:50 -0700 [thread overview]
Message-ID: <20030804154150.GB30195@work.bitmover.com> (raw)
In-Reply-To: <1060011549.900.50.camel@thor.holligenstrasse29.lan>
On Mon, Aug 04, 2003 at 05:39:09PM +0200, Michel D?nzer wrote:
> On Mon, 2003-08-04 at 17:26, Larry McVoy wrote:
> > > Here is what I have in a tree locally to go to Linus. I can't push it
> > > out because ppc.bkbits.net seems to be down.
> >
> > It's back. If anyone has any insight into how to track down kernel hangs
> > I'd love to hear them. bkbits.net has been flakey in the last couple of
> > months and sometimes just hangs, last night's was with pings still working
> > but no response at the console.
>
> Which kernel is it running? Something like this happened to every 2.4.21
> kernel I've tried soon after they hit swap. I thought it might be a bad
> interaction of the 2.4.21 VM, CONFIG_HIGHMEM and the XFS and whatnot
> patches and went back to good old 2.4.20-ben8.
2.4.20 and I am using CONFIG_HIGHMEM. It's on a serverworks chipset and
maybe that's causing problems. I need to get off IDE.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-04 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 21:56 2.6.0-test2-bk2 (linus' tree) -- arch/ppc/platforms/pmac_cpufreq.c:219: undefined reference to `cpufreq_frequency_table_verify' Miles Lane
2003-08-03 22:01 ` Benjamin Herrenschmidt
2003-08-03 22:15 ` Miles Lane
2003-08-03 22:17 ` Miles Lane
2003-08-04 11:34 ` Paul Mackerras
2003-08-04 15:26 ` Larry McVoy
2003-08-04 15:39 ` Michel Dänzer
2003-08-04 15:41 ` Larry McVoy [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=20030804154150.GB30195@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).