On Mon, 2005-08-08 at 22:24 +0500, Fawad Lateef wrote:
> Dear Arjan,
>
> On 8/8/05, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> >
> > 1) you probably should use RH support for this
> > 2) you forgot to attach your sourcecode / URL to that, including the
> >full source of your module.
> >
>
Dear Arjan,
On 8/8/05, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
>
> 1) you probably should use RH support for this
> 2) you forgot to attach your sourcecode / URL to that, including the
>full source of your module.
>
I already mentioned my code and some details in my previous mail on
the
On Mon, 2005-08-08 at 08:50 +0500, Fawad Lateef wrote:
> Hello,
>
> I m facing a problem in RHEL3 (2.4.21-5.ELsmp) kernel while using
> kmap_atomic on the pages reserved at the boot time
>
> At the boot time I reserved pages above 2GB for later use by my module
> . And when I was using t
Fawad Lateef wrote:
if ((unsigned long)(page - mem_map) > 0x8) {
SetPageReserved(page);
set_bit(PG_highmem, &page->flags);
atomic_set(&page->count, 0xC4);
That seems like a hackish thing to do. Could you mistake other pages
with
On 8/8/05, Zachary Amsden <[EMAIL PROTECTED]> wrote:
>
> IIRC 2.4.21 has some highmem bugs that have since been fixed. But, it
> sounds like you might be doing something quite unusual. Code would
> definitely give people a better idea of what might be wrong.
I think you overlooked what i ment
Fawad Lateef wrote:
Hello,
I m facing a problem in RHEL3 (2.4.21-5.ELsmp) kernel while using
kmap_atomic on the pages reserved at the boot time
At the boot time I reserved pages above 2GB for later use by my module
. And when I was using those reserved pages through kmap_atomic
system
On 8/7/05, Fawad Lateef <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I m facing a problem in RHEL3 (2.4.21-5.ELsmp) kernel while using
> kmap_atomic on the pages reserved at the boot time
Unless you can reproduce this in a current kernel.org kernel
(2.6.13-rc6), then you probably should contact R
7 matches
Mail list logo
