I had other inconsistent behavior in my system (mostly while web browsing
with firefox), and suspected from AVG Free antivirus (its resident process
running all the time at about 30% of CPU consumption)
Then, I uninstalled AVG and installed ESET NOD32.
Now Wireshark behaves smoothly and I can't reproduce the error anymore.
Who knows...

Thank you all !

Rodrigo.

On Tue, Jan 19, 2010 at 1:58 PM, Gianluca Varenni <
[email protected]> wrote:

>  That's a totally different story, then...
>
> Can you take a screenshot of the performance tab in task manager and send
> it to me privately?
>
> Have a nice day
> GV
>
>
>  *From:* Ing. Rodrigo Castro <[email protected]>
> *Sent:* Tuesday, January 19, 2010 4:12 AM
> *To:* Gianluca Varenni <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: [Wireshark-dev] read error: PacketReceivePacket failed
>
> Sorry I didn´t make this clear before: I can't even start a capture, the
> error rises as soon as I press Start.
>
> By the way, because the capture gets aborted at the very beggining, a
> second message windows appears (along with the one that contains the
> original message reported in this mails);
>
> "
> No packets captured!
> As no data was captured, closing the temporary capture file!
> Help about capturing can be found at:
>        http://wiki.wireshark.org/CaptureSetup
> Wireless (Wi-Fi/WLAN):
> Try to switch off promiscuous mode in the Capture Options!
> "
>
> I do not understand why it suggests to do something with the Wireless
> interface (which I have turned off) if I am trying to capture with the LAN
> interface...
>
> This is all I have for now.
>
> Thanks !
>
>
> On Mon, Jan 18, 2010 at 1:31 PM, Gianluca Varenni <
> [email protected]> wrote:
>
>>  Since you can reproduce it consistently, does it happen after having
>> captured for a long time?
>>
>> Have a nice day
>> GV
>>
>>  *From:* Ing. Rodrigo Castro <[email protected]>
>> *Sent:* Saturday, January 16, 2010 11:05 AM
>> *To:* [email protected]
>>   *Subject:* Re: [Wireshark-dev] read error: PacketReceivePacket failed
>>
>> Thanks all for the answers.
>> Gianluca:
>>
>> > - can you reproduce it consistently?
>>
>> Yes
>>
>> > - did it happen after capturing hours and hours?
>>
>> No
>>
>> > - if it's a USB network adapter, did you disconnect it?
>>
>> No
>>
>> > - did it happen after getting your PC out of hibernation?
>>
>> No
>>
>> I also updated the Broadcom 440 NIC Win XP controllers to the latest
>> release, and reproduced the same behavior booting with Dell WinXP Media
>> Center, and also with a WinXP UE.
>>
>> Regards,
>> Rodrigo.
>>
>>
>> Message: 3
>> Date: Fri, 15 Jan 2010 15:00:38 -0800
>> From: "Gianluca Varenni" <[email protected]
>> >
>> Subject: Re: [Wireshark-dev] read error: PacketReceivePacket failed
>> To: "Developer support list for Wireshark"
>>        <[email protected]>
>> Message-ID: <6641c1031f154c00b0dc8e1aa3b15...@nelson3>
>> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>>        reply-type=original
>>
>> Well, it can mean everything...
>>
>> - can you reproduce it consistently?
>> - did it happen after capturing hours and hours?
>> - if it's a USB network adapter, did you disconnect it?
>> - did it happen after getting your PC out of hibernation?
>>
>> GV
>>
>>
>> --------------------------------------------------
>> From: "Guy Harris" <[email protected]>
>> Sent: Friday, January 15, 2010 1:59 PM
>> To: "Developer support list for Wireshark" <[email protected]>
>> Subject: Re: [Wireshark-dev] read error: PacketReceivePacket failed
>>
>> >
>> > On Jan 14, 2010, at 12:51 PM, Ing. Rodrigo Castro wrote:
>> >
>> >> Hi all. I am getting the following error:
>> >>
>> >> "
>> >> Error while capturing packets: read error: PacketReceivePacket failed
>> >> Please report this to the Wireshark developers.
>> >> (This is not a crash; please do not report it as such.)
>> >> "
>> >
>> > That's an error in WinPcap; you should probably ask the WinPcap
>> developers
>> > about it:
>> >
>> > http://www.winpcap.org/contact.htm
>> >
>> > or perhaps Gianluca will respond here.
>> >
>> ___________________________________________________________________________
>> > Sent via:    Wireshark-dev mailing list <[email protected]>
>> > Archives:    http://www.wireshark.org/lists/wireshark-dev
>> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>> >             mailto:[email protected]
>> ?subject=unsubscribe
>>
>>
>>
>> --
>> Ing. Rodrigo Castro
>> -
>> PhD Student
>> Laboratory for System Dynamics and Signal Processing
>> http://www.fceia.unr.edu.ar/lsd/
>> Escuela de Ingeniería Electrónica
>> Facultad de Ciencias Exactas, Ingeniería y Agrimensura
>> Universidad Nacional de Rosario, Argentina.
>> -
>> "Computers are useless. They can only give you answers" - Pablo Picasso
>>
>> ------------------------------
>>
>>
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <[email protected]>
>> Archives:    http://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>              mailto:[email protected]
>> ?subject=unsubscribe
>>
>
>
>
> --
> Ing. Rodrigo Castro
> -
> PhD Student
> Laboratory for System Dynamics and Signal Processing
> http://www.fceia.unr.edu.ar/lsd/
> Escuela de Ingeniería Electrónica
> Facultad de Ciencias Exactas, Ingeniería y Agrimensura
> Universidad Nacional de Rosario, Argentina.
> -
> "Computers are useless. They can only give you answers" - Pablo Picasso
>



-- 
Ing. Rodrigo Castro
-
PhD Student
Laboratory for System Dynamics and Signal Processing
http://www.fceia.unr.edu.ar/lsd/
Escuela de Ingeniería Electrónica
Facultad de Ciencias Exactas, Ingeniería y Agrimensura
Universidad Nacional de Rosario, Argentina.
-
"Computers are useless. They can only give you answers" - Pablo Picasso
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to