linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Highmem on PPC?
Date: Fri, 8 Feb 2002 10:36:00 -0700	[thread overview]
Message-ID: <20020208103600.B24460@boardwalk> (raw)
In-Reply-To: <20020205193316.19866@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Tue, Feb 05, 2002 at 08:33:16PM +0100


On Tue, Feb 05, 2002 at 08:33:16PM +0100, Benjamin Herrenschmidt wrote:
>
> And let me know if you find something ;)

In my quest for a non-SCSI block device, I tried using loopback over
NFS. :) Okay, loopback doesn't normally work, and it's not surprising
that it doesn't work over NFS with highmem enabled.  If anyone is
interested, this script immediately crashes on the latest 2_4_devel,
only with NFS mounted root and with some memory in highmem:

#!/bin/bash
dd if=/dev/zero of=file bs=1024 count=10000
losetup /dev/loop0 file
mke2fs /dev/loop0

Exception info and backtrace from xmon (I have sysmap included on
Gemini):

1:mon> e
cpu 1: vector: 300 at pc = c001239c (T memcpy+0x24), lr = c00d5b9c (t transfer_none+0x40)
msr = 9032, sp = df9fdf60 [df9fdeb0]
dar = 0, dsisr = 42000000
current = df9fc000, pid = 426, comm = loop0
1:mon> t
backtrace:
c00899e4 (t nfs_prepare_write+0x10)
c00d5e5c (t lo_send+0x13c)
c00d6278 (t do_bh_filebacked+0x98)
c00d6ba0 (t loop_thread+0x194)
c00076b8 (T kernel_thread+0x2c)

I suspect that nfs_prepare_write is not properly kmapping/kunmapping
something.

If anyone else feels like fixing this, feel free... It's not high on
my list of priorities. :)

-VAL

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2002-02-08 17:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05  1:32 Highmem on PPC? Val Henson
2002-02-05 12:52 ` benh
2002-02-05 18:56   ` Val Henson
2002-02-05 19:33     ` Benjamin Herrenschmidt
2002-02-05 19:42       ` Val Henson
2002-02-05 19:47         ` Benjamin Herrenschmidt
2002-02-07 12:27       ` Christopher Murtagh
2002-02-07 21:43       ` Val Henson
2002-02-07 21:51         ` Benjamin Herrenschmidt
2002-02-07 21:56           ` Val Henson
2002-02-07 21:59             ` Benjamin Herrenschmidt
2002-02-07 21:53         ` Mark A. Greer
2002-02-07 21:58           ` Val Henson
2002-02-07 23:09             ` Mark A. Greer
2002-02-08  3:02         ` Tom Rini
2002-02-08  6:05         ` Christopher Murtagh
2002-02-08  6:25           ` Val Henson
2002-02-08 17:36       ` Val Henson [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=20020208103600.B24460@boardwalk \
    --to=val@nmt.edu \
    --cc=linuxppc-dev@lists.linuxppc.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).