Brian n1uro wrote in the news group that he had problems with “ifconfig rose0 down”. Now I have also experienced this problem. And even a “kernel panic” with fpac.
First the piece of Brian n1uro.
If you run rose and try to "ifconfig rose0 down" or if you try to remove the module: Nov 27 23:18:10 n1uro kernel: [398645.598318] unregister_netdevice: waiting for rose0 to become free. Usage count = 556 Nov 27 23:18:20 n1uro kernel: [398655.836006] unregister_netdevice: waiting for rose0 to become free. Usage count = 556 Nov 27 23:18:30 n1uro kernel: [398666.073800] unregister_netdevice: waiting for rose0 to become free. Usage count = 556 Nov 27 23:18:41 n1uro kernel: [398676.311558] unregister_netdevice: waiting for rose0 to become free. Usage count = 556 ^Cn1uro@n1uro:~$ The kernel goes into an endless loop every 10 seconds. This began in 3.x series kernels. On 4.2=< it tends to panic.
“ifconfig rose0 down” seems to work. But if you try again a “rsattach” you will see that he takes “rose1”. Try it against “mobprobe -r rose” and you immediately get an “unregister_netdevice”. Fairly annoying.
Here we come to the “kernel panic”. After starting and stopping fpac, it means that the rose0 interface has not been released. If you then make a rose connection from uronode to fpac you get a “kernel panic”
pd2lt@uro.pd2lt.ampr.org-IPv6: fpac Trying pi1lap-6 @ 2040330113... <Enter> aborts. Message from syslogd@gw at Nov 28 15:40:33 ... kernel:[121671.208449] Oops: 0000 [#1] SMP Message from syslogd@gw at Nov 28 15:40:33 ... kernel:[121671.211078] Process fpacwpd (pid: 5892, ti=f580a000 task=f4df7ae0 task.ti=f4f7e000) Message from syslogd@gw at Nov 28 15:40:33 ... kernel:[121671.211207] Stack: Message from syslogd@gw at Nov 28 15:40:33 ... kernel:[121671.211780] Call Trace: Message from syslogd@gw at Nov 28 15:40:33 ... kernel:[121671.212007] <IRQ>
After stopping and starting fpac, syslog / user.log is fully spammed. It was even so bad that I got an email from my system in one day that the disk was full. Helppppppp ….. panic
Syslog and user.log were a few gigabytes in size.
Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw rsyslogd-2177: imuxsock lost 884 messages from pid 5960 due to rate-limiting Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw fpad: accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument Nov 29 14:37:43 gw fpacroute: FPAC fpacroute accept error Invalid argument
So do not stop fpac en restart it again. Reboot the system to free the rose interface. Unfortunately