From: Jens Axboe <axboe@suse.de>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: chaffee@cs.berkeley.edu, linux-kernel@vger.kernel.org
Subject: Re: Kernel Panic: too few segs for DMA mapping increase AHC_NSEG
Date: Tue, 27 Nov 2001 09:11:37 +0100 [thread overview]
Message-ID: <20011127091137.Z5129@suse.de> (raw)
In-Reply-To: <LAW2-OE64dLLZfOfAD200002cce@hotmail.com>
In-Reply-To: <LAW2-OE64dLLZfOfAD200002cce@hotmail.com>
On Tue, Nov 27 2001, Marco Berizzi wrote:
> I have upgraded my PC from 768MB RAM to 1GB.
> I have recompiled the kernel (2.4.16) for hi mem support (4GB).
>
> I have several file system on the same disk (vfat file system). I have
> compiled vfat driver both in the main kernel and as a module. When I
> load the module I issue a
> 'modprobe vfat' and I get this message (only with hi mem kernel
> support):
>
> Warning: loading /lib/modules/2.4.16/kernel/fs/vfat/vfat.o will taint
> the kernel: no license
> I'm using Slackware 8.0. + modutils 2.4.12
>
> 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
>
> Kernel panic: too few segs for DMA mappings increase AHC_NSEG
You still haven't applied the patch I sent? Sending the same report
without this extra added infor 2 or 3 times isn't doing any good, sorry.
--
Jens Axboe
next prev parent reply other threads:[~2001-11-27 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 8:02 Kernel Panic: too few segs for DMA mapping increase AHC_NSEG Marco Berizzi
2001-11-27 8:11 ` Jens Axboe [this message]
2001-11-27 19:59 ` Marco Berizzi
[not found] <200112130644.fBD6ibI83062@saturn.cs.uml.edu>
2001-12-13 8:07 ` Marco Berizzi
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 15:18 Marco Berizzi
2001-11-23 21:26 Marco Berizzi
2001-11-19 8:23 Marco Berizzi
2001-11-19 9:44 ` Jens Axboe
2001-11-21 7:46 ` 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=20011127091137.Z5129@suse.de \
--to=axboe@suse.de \
--cc=chaffee@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.com \
/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