as soon as airmon-ng tries to put my
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
in passive mode, i get a kernel panic.
A screen shot taken with my phone is attacched
sorry, couldn't upload the picture. You can find it here
Created attachment 38972 [details]
What kernel are you running?
2.6.36. Should i update it?
bool "Timestamping in PHY devices"
depends on EXPERIMENTAL
This allows timestamping of network packets by PHYs with
hardware timestamping capabilities. This option adds some
overhead in the transmit and receive paths.
If you are unsure how to answer this question, answer N.
In the shortrun, you might try turning that off in your .config.
Wey-yi, it looks like iwl3945 isn't leaving enough headroom in the skb for the skb_push in skb_defer_rx_timestamp?
The following three bugs are all duplicates of each other:
They all have the same root cause, and all are fixed by the patch
posted by Eric Dumazet on netdev:
The work-around is to disable CONFIG_NETWORK_PHY_TIMESTAMPING.
*** This bug has been marked as a duplicate of bug 24102 ***