Bug 24292

Summary: kernel panic while using airmon-ng and iwl3945
Product: Drivers Reporter: filippo (f)
Component: network-wirelessAssignee: drivers_network-wireless (drivers_network-wireless)
Severity: high CC: f, florian, linville, maciej.rutecki, richardcochran, rjw, wey-yi.w.guy
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.36 Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 16444    
Attachments: 03122010253.jpg

Description filippo 2010-12-03 17:42:20 UTC
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
Comment 1 filippo 2010-12-03 17:44:45 UTC
sorry, couldn't upload the picture. You can find it here
Comment 2 John W. Linville 2010-12-03 18:57:56 UTC
Created attachment 38972 [details]
Comment 3 John W. Linville 2010-12-03 18:58:22 UTC
What kernel are you running?
Comment 4 filippo 2010-12-03 22:24:44 UTC
2.6.36. Should i update it?
Comment 5 John W. Linville 2010-12-06 19:53:58 UTC
        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?
Comment 6 wey-yi.w.guy 2010-12-06 21:38:40 UTC
netdev patch 


Comment 7 Richard Cochran 2010-12-10 14:26:19 UTC
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.                  
Comment 8 John W. Linville 2010-12-10 14:28:01 UTC

*** This bug has been marked as a duplicate of bug 24102 ***