From: Peter Horton <pdh@colonel-panic.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Peter Horton <phorton@bitbox.co.uk>, linux-mips@linux-mips.org
Subject: Re: Kernel 2.4.23 on Cobalt Qube2 - area of problem
Date: Sat, 13 Dec 2003 18:38:32 +0000 [thread overview]
Message-ID: <20031213183832.GA12439@skeleton-jack> (raw)
In-Reply-To: <20031213170751.GB13271@linux-mips.org>
On Sat, Dec 13, 2003 at 06:07:51PM +0100, Ralf Baechle wrote:
> On Fri, Dec 12, 2003 at 10:45:08AM +0000, Peter Horton wrote:
>
> > More info on the random segmentation faults and data corruption on my Qube2.
> >
> > 2.4.21 from CVS is the first kernel to exhibit the problem. I tracked it
> > down to the cache handling changes that went in between 2.4.20 and 2.4.21.
> >
> > By (not very scientifically) removing flush_dcache_page() and
> > re-instating flush_page_to_ram() I managed to get the 2.4.21 kernel
> > stable (see attached patch). Applying a similiar patch to 2.4.23 (CVS
> > HEAD) allows me to run 2.4.23 too.
> >
> > I don't know how to track the problem any further - the kernel's cache
> > handling is a bit out of my league.
> >
> > Anyone got a clue stick they can point me in the right direction with ?
>
> Can you put a printk into c-r4k.c and print the value of the
> shm_align_mask variable? I want to make sure it's got a sane value on
> your box. Also the first few lines of your bootup messages with the
> processor and cache stuff would be useful.
>
I've just tried changing pages_do_alias() to always return non-zero. The
resulting kernel is still unstable - segmentation faults when loading
shared libraries, signal 11 when compiling etc.
P.
prev parent reply other threads:[~2003-12-13 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 10:45 Kernel 2.4.23 on Cobalt Qube2 - area of problem Peter Horton
2003-12-13 17:07 ` Ralf Baechle
2003-12-13 18:20 ` Peter Horton
2003-12-13 18:38 ` Peter Horton [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=20031213183832.GA12439@skeleton-jack \
--to=pdh@colonel-panic.org \
--cc=linux-mips@linux-mips.org \
--cc=phorton@bitbox.co.uk \
--cc=ralf@linux-mips.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