From: Filippo Zangheri <filippo.zangheri@yahoo.it>
To: Michael Leun <linux-wireless@newton.leun.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: compat wireless, i3945, tcpdump: Machine freezes
Date: Wed, 18 Jun 2008 11:39:23 +0200 [thread overview]
Message-ID: <4858D7CB.1080603@yahoo.it> (raw)
In-Reply-To: <20080618094213.5abd2fbd@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Leun ha scritto:
> Hello,
>
> I downloaded compat-wireless-2008-06-18, built it, loaded cfg80211.ko,
> mac80211.ko, iwl3945.ko, associated to an ap, started "tcpdump -i wlan0
> -n" and the machine mostly freezed.
>
> Mostly means keyboard does not work, no disk-access, no network but
> mouse still works.
>
> This is reproducable, freeze happens instantly after starting tcpdump
> (if a ping runs while I start tcpdump I see one Packet in the output of
> tcpdump, then machine is frozen).
>
> I've had that with some older versions of compat-wireless also.
Same behaviour here.
I add that the freezes happen when the card is associated to the AP.
They happen with tcpdump and with wireshark, both selecting wmaster0
and wlan0 interfaces; but don't happen with kismet.
Furthermore, I have a PPPoE Internet connection and the computer
freezes even when I try to monitor ppp0 interface (when the PPPoE
connection uses the radio link).
Thanks.
- --
Filippo Zangheri
GPG key ID: 0x6C1F2F2F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIWNfLjzxMG2wfLy8RAl1IAJ0cOPq2dYMrSkbI4FYeIUGj1RMrLQCeOxaV
CHibU4ueXOnQpOv737f12oI=
=mk9X
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-06-18 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 7:42 compat wireless, i3945, tcpdump: Machine freezes Michael Leun
2008-06-18 9:39 ` Filippo Zangheri [this message]
2008-06-25 13:43 ` linux-wireless
2008-06-26 1:02 ` Zhu Yi
2008-06-27 18:04 ` linux-wireless
[not found] ` <48660294.2010405@yahoo.it>
2008-06-29 22:17 ` Michael Leun
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=4858D7CB.1080603@yahoo.it \
--to=filippo.zangheri@yahoo.it \
--cc=linux-wireless@newton.leun.net \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).