Sid,
I was wondering if you or anyone else have tried SP3...
Cristian
Sid Van den Heede wrote:
>
> This has been a long outstanding problem. I have been dealing with it for
> months, and am no further ahead. I have supplied my complete rulebase to my
> vendor, so surely they or Checkpoint could reproduce the problem. Given the
> number of people on this list with the same problem, it behooves Checkpoint to
> act...NOW!
>
> FW1 is trying to allocate a chunk of kernel memory that, in the example below,
> is 275,548 bytes. The maximum size of a block of kernel memory that Linux 2.2
> will allocate is 128KB. There are ways to get bigger chunks of memory, but not
> via kmalloc.
>
> I tried increasing the cache sizes table, but the kernel failed to initialize
> the cache at boot time, and promptly halted. This is due to the number of bits
> that are allocated for a combination of page size and chunk size. An obscure
> reference suggested that it could be possible to create a class of memory that
> would accommodate larger sizes. Kernel experts anyone?
>
> Thanks for the clue about fwhmem on the fwinsmod line. I tried it, but going
> in the opposite direction. I added fwhmem=128000, a number less than 128KB,
> just to see if that would limit the amount of memory that fwd tries to
> allocate. Unfortunately it had no impact.
>
> At this point it appears that the options are:
>
> 1. Get Checkpoint to fix the code.
>
> 2. Get Checkpoint to fix the code.
>
> 3. Use a trivial rulebase. I tried one with about a dozen entries. That
> wasn't small enough, but it was necessary to accommodate our requirements.
>
> 4. Get Checkpoint to fix the code.
>
> 5. Work on a way for kmalloc to allocate more memory.
>
> 6. Get Checkpoint to fix the code.
>
> 7. Use another platform (Solaris, etc).
>
> Did I mention that Checkpoint should fix the code?
>
> BTW, has anybody seen this on the Linux-based appliances, such as the PDS-2100
> fron intrustion.com?
>
> On Wed, 17 Jan 2001, cristian nicolae wrote:
>
> > Date: Wed, 17 Jan 2001 23:28:50 +0100
> > From: cristian nicolae <[EMAIL PROTECTED]>
> > To: Eugene Alperovich <[EMAIL PROTECTED]>
> > Cc: "'[EMAIL PROTECTED]'"
> > <[EMAIL PROTECTED]>
> > Subject: Re: [FW1] Strange things in RH62 + Fw1-41-Sp2( kmalloc: Size
> > (275548) too large )
> >
> >
> > Hi Eugene,
> > I had that too.
> > Generally, at least in my case, this appeared after I loaded
> > a huge security policy. Other people had that too. Until now I could not
> > see any pointers to a final solution. Maybe it's worth trying SP3.
> >
> > Cristian
> >
> >
> >
> > Eugene Alperovich wrote:
> > >
> > > Hi all,
> > >
> > > We have been having this thing with a RH62 running Fw1-4.1-SP2,
> > > when I check the kernel Log, I see the following lines repeating themselves
> > > hundreds of times:
> > >
> > > Jan 17 07:48:48 firewall kernel: kmalloc: Size (275548) too large
> > > Jan 17 07:48:48 firewall kernel: FW-1: b_getvals: fw_kmalloc(275536) failed
> > > Jan 17 07:48:48 firewall kernel: kmalloc: Size (275548) too large
> > > Jan 17 07:48:48 firewall kernel: FW-1: b_getvals: fw_kmalloc(275536) failed
> > >
> > > The numbers never change.
> > > We tried including the "fwhmem=5000000" option in the fwinsmod on boot, but
> > > to no avail.
> > >
> > > Did anyone ever see this?
> > >
> > > Eugene Alperovich, Integrator,
> > > Xpert Trusted Systems Ltd.
> > > e-mail: [EMAIL PROTECTED]
> > > <<MyVCARD.vcf>>
> >
> >
> > ================================================================================
> > To unsubscribe from this mailing list, please see the instructions at
> > http://www.checkpoint.com/services/mailing.html
> > ================================================================================
> >
>
> ------------------------------------------------------------------
> Sid Van den Heede Open Text Corporation
> +1 519 888 7111 x2211 185 Columbia Street West
> +1 519 888 0677 (fax) Waterloo, Ontario, Canada N2L 5Z5
> [EMAIL PROTECTED] OpenPGP key available on www.keyserver.net
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================