mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Marco Berizzi" <pupilla@hotmail.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel Panic: too few segs for DMA mapping increase AHC_NSEG
Date: Mon, 19 Nov 2001 09:23:27 +0100	[thread overview]
Message-ID: <LAW2-OE70z82buW5RNB000007e5@hotmail.com> (raw)

Hi everybody.

I have just upgraded my PC from 768MB RAM to 1GB.
I have recompiled the kernel (2.4.14) for hi mem support (4GB).

Now it's appening a very strange behaviour.
I have several file system on the same disk (vfat file system). I have
compiled vfat driver as a module. So before try to mount I must issue a
'modprobe vfat'. I'm using Slackware 8.0. modutils version is 2.4.6

Then if I try to copy a file from that filesystem to the root filesystem
I get this error:

Kernel panic: too few segs for DMA mappings increase AHC_NSEG

Usually this is the procedure:

root login
modprobe vfat
mount /dev/sda2 /mnt   (to mount the fat partition)
cd /usr/src
cp /mnt/linux/kernel/linux-2.2.20.tar.bz2 . (I want to copy kernel
source tarball from the vfat partition to /usr/src)
CRASH..........

My MB is ABIT KT7A (bios rev ID 65  11/07/2001). Two 512 MB SDRAM
(takei).
Other HW: AHA 39160, SCSI IBM HD DDYS 18130, Matrox G450.
gcc version 2.95.3, binutils 2.10.91.0.4 (***not the original slack
8.0***, I have downgraded it for Oracle 9i)

If I compile a kernel without hi mem support all is fine.

             reply	other threads:[~2001-11-19  8:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19  8:23 Marco Berizzi [this message]
2001-11-19  9:44 ` Jens Axboe
2001-11-21  7:46   ` Marco Berizzi
2001-11-23 21:26 Marco Berizzi
2001-11-24 15:18 Marco Berizzi
2001-11-27  8:02 Marco Berizzi
2001-11-27  8:11 ` Jens Axboe
2001-11-27 19:59   ` Marco Berizzi
     [not found] <200112130644.fBD6ibI83062@saturn.cs.uml.edu>
2001-12-13  8:07 ` Marco Berizzi

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=LAW2-OE70z82buW5RNB000007e5@hotmail.com \
    --to=pupilla@hotmail.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

all inboxes | Powered by JetHome®