Ok, it's happened again.  I'm getting the "not enough memory to allocate
the kernel buffer" error again.

My kernel memory statistics:

Total: 113,300 Kb
Paged: 38,004 Kb
Nonpaged: 75,316 Kb

Doesn't seem too drastic to me.  I'm not sure what else to check.

Now I can't use Ethereal or Windump until I reboot.

> -----Original Message-----
> From: Joel Moore [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, April 13, 2004 9:46 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [WinPcap-users] Kernel Buffer Error
> 
> 
> Thanks, I'll keep an eye on it and report back when it 
> happens again.  However, if I was running out of kernel 
> memory wouldn't I be seeing problems elsewhere?
> 
> Do you know if there's any way to track how much kernel 
> memory each service is using?  XP doesn't seem to offer that 
> kind of granularity.
> 
> Just for the record, my current kernel memory statistics 
> (approximate):
> 
> Total:        101,904 Kb
> Paged:         40,828 Kb
> Non-paged:     61,100 Kb
> 
> I tried Ethereal a few times and received no errors.
> 
> 
> > -----Original Message-----
> > From: Gianluca Varenni [mailto:[EMAIL PROTECTED] 
> > Sent: Tuesday, April 13, 2004 9:08 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [WinPcap-users] Kernel Buffer Error
> > 
> > 
> > Hi.
> > 
> > Are you using the latest version of WinPcap (3.1beta)? Can 
> > you please have a
> > look at the memory usage of your system on the Task Manager, 
> > in particular
> > the items "Paged" and "NonPaged" in the kernel memory part of 
> > the mem usage?
> > 
> > A user reported a similar problem, and it was actually due to 
> > a service
> > leaking some resources. The consequence was that WinPcap was 
> > not able to
> > allocate the appropriate resources for its work.
> > 
> > Have a nice day
> > GV
> > 
> 




==================================================================
 This is the WinPcap users list. It is archived at
 http://www.mail-archive.com/[EMAIL PROTECTED]/

 To unsubscribe use 
 mailto: [EMAIL PROTECTED]
==================================================================

Reply via email to