1 2 Previous Next 18 Replies Latest reply on Mar 30, 2015 12:27 PM by paulroyal

    Edison Networking Issue (protocol 0000 is buggy, dev wlan0)

    paulroyal

      When scanning a network (e.g., using ARP requests via arp-scan) on the Edison with various official images (edison-image-rel1-maint-rel1-ww42-14, edison-image-ww05-15), the following messages appear in dmesg.

       

      [  266.844585] protocol 0000 is buggy, dev wlan0

      [  266.848916] protocol 0000 is buggy, dev wlan0

      [  266.853300] protocol 0000 is buggy, dev wlan0

      [  266.857663] protocol 0000 is buggy, dev wlan0

      [  266.862047] protocol 0000 is buggy, dev wlan0

      [  266.866376] protocol 0000 is buggy, dev wlan0

      [  266.870718] protocol 0000 is buggy, dev wlan0

      [  266.875104] protocol 0000 is buggy, dev wlan0

      ...

      [  669.763512] net_ratelimit: 498 callbacks suppressed

      [  669.763539] protocol 0000 is buggy, dev wlan0

      [  669.768448] protocol 0000 is buggy, dev wlan0

      [  669.772750] protocol 0000 is buggy, dev wlan0

      [  669.777121] protocol 0000 is buggy, dev wlan0

      [  669.781503] protocol 0000 is buggy, dev wlan0

      [  669.785815] protocol 0000 is buggy, dev wlan0

      [  669.790213] protocol 0000 is buggy, dev wlan0

       

      The first time a program generating a scan is run, messages similar to the following also appear.

       

      [  266.831804] BUG: scheduling while atomic: arp-scan/321/0x00000101

      [  266.831859] Modules linked in: usb_f_acm u_serial g_multi libcomposite bcm_bt_lpm bcm4334x(O)

      [  266.831924] CPU: 1 PID: 321 Comm: arp-scan Tainted: G           O 3.10.17-poky-edison+ #1

      [  266.831938] Hardware name: Intel Corporation Merrifield/BODEGA BAY, BIOS 466 2014.06.23:19.20.05

      [  266.831952]  f51b6f40 f51b6f40 f6f8fea0 c18a1334 f6f8febc c189d1fb c1a9a0d8 f51b7240

      [  266.832003]  00000141 00000101 00000000 f6f8ff3c c18a5877 c1247206 c646f04c f6f8e000

      [  266.832052]  c646efb6 f6f8e000 c1cc6940 f6f8e000 00000000 f73fd940 f51b6f40 c646f04c

      ...

       

      Similar results are produced when using nmap to perform a ping scan. These messages seem to correspond to events that introduce instability into the system, as the Edison has subsequently become unresponsive on multiple occasions.

       

      Does anyone know if there is a newer Edison image that resolves this issue?

        1 2 Previous Next