search

seemoo-lab / nexmon

The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more
GNU General Public License v3.0
2.47k stars 457 forks source link

nexutil error: Segmentation Fault; Internal error: Oops: 17 [#1] SMP ARM #71

Open JBaczuk opened 7 years ago

JBaczuk commented 7 years ago

I had monitor mode working. But, when I try to run $ nexutil -m2 after a reboot, (first I have to reload the module). Then I get this error:

pi@pi1:~/Downloads/nexmon/patches/bcm43438/7_45_41_26/nexmon $ nexutil -m2Segmentation fault
pi@pi1:~/Downloads/nexmon/patches/bcm43438/7_45_41_26/nexmon $ 
Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854103] Internal error: Oops: 17 [#1] SMP ARM

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854448] Process nexutil (pid: 1137, stack limit = 0xb0264210)

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854459] Stack: (0xb0265db0 to 0xb0266000)

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854473] 5da0:                                     7f364e4c b0265dcc b011fa00 7f364e4c

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854490] 5dc0: b011fa10 000004c0 b0265e04 b0265dd8 7f34df38 7f3473c4 00000014 00000024

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854507] 5de0: b0077800 b6fddc00 b0077800 00000024 b8990480 00000000 b0265e34 b0265e08

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854524] 5e00: 80507d74 7f34ddd4 00000000 7fffffff b0077800 b0265ec4 b0077800 00000000

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854541] 5e20: 00000024 00000000 b0265e94 b0265e38 80508240 80507bec 804be7d0 805bc4a8

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854559] 5e40: b99e7848 00000000 b988b268 00000000 b0077a8c b88d9000 00000000 00000471

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854575] 5e60: 000003e8 000003e8 80505ddc 00000000 00000000 b7716780 00000121 8000fd28

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854592] 5e80: b0264000 00000000 b0265ea4 b0265e98 804ba988 80507f0c b0265f8c b0265ea8

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854609] 5ea0: 804bba0c 804ba970 b0265ecc b0265eb8 805061bc fffffff7 00000000 01fe0b58

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854625] 5ec0: 00000024 00000000 00000000 00000001 00000000 00000000 b0265ec4 00000000

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854642] 5ee0: 00000000 00000000 00000000 01fe0b38 b0265fa4 b0265f00 804bb7c8 805061f0

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854659] 5f00: 00000000 00000000 00000010 00000000 00000000 00000011 b7716900 7e919e40

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854677] 5f20: b0265f6c b0265f30 804c04c8 804be6cc b0265f74 8017506c b0265f54 b0265f48

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854693] 5f40: 8017506c 00000008 00000001 b7716900 7e919e40 00000014 b0264000 00000000

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854710] 5f60: b0265fa4 b0265f70 804bbc48 804c0234 00000008 7e91a210 00000000 00000000

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854726] 5f80: b0265fa4 b0265f90 804bba5c 804bb950 00000000 00000000 00000000 b0265fa8

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854743] 5fa0: 8000fb60 804bba40 7e91a210 00000000 00000003 01fe0b58 00000024 00000000

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854760] 5fc0: 7e91a210 00000000 00000000 00000121 00000000 00014b90 00014c30 7e919e2c

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.854776] 5fe0: 00000000 7e919de4 00013ca0 0002da9c 40000010 00000003 00000000 00000000

Message from syslogd@pi1 at Apr  8 07:57:57 ...
 kernel:[   95.855121] Code: e24dd008 e52de004 e8bd4000 e1a04000 (e5900000)

I have tried reinstalling firmware back to the source setup_env.sh command, but still same error.

JBaczuk commented 7 years ago

I can confirm that following the script in #67 does allow it to work again, but only if you reload the module.