|
||||||||
As always, thank you for reading! I'm seeing an error in our m0n0 logs that I haven't seen before. Since seeing this error, our Soekris net5501-60 running v1.235 has been locking up randomly-roughly once per day-requiring a reboot. Here is a sample of the log entries in question: Nov 17 18:18:45 /kernel: usb0: 1 scheduling overruns Nov 17 18:18:40 /kernel: usb0: 1 scheduling overruns Nov 17 18:18:32 /kernel: vr0: rx packet lost Nov 17 18:18:32 /kernel: usb0: 1 scheduling overruns Nov 17 18:18:24 /kernel: vr0: rx packet lost Nov 17 18:18:24 /kernel: usb0: 1 scheduling overruns Nov 17 18:18:22 /kernel: vr0: rx packet lost Nov 17 18:18:22 /kernel: usb0: 1 scheduling overruns Nov 17 18:17:47 /kernel: usb0: 2 scheduling overruns Nov 17 18:17:43 /kernel: vr0: rx packet lost Nov 17 18:17:43 /kernel: usb0: 1 scheduling overruns Nov 17 18:17:40 /kernel: vr0: rx packet lost Nov 17 18:17:40 /kernel: usb0: 1 scheduling overruns Nov 17 18:17:39 /kernel: usb0: 1 scheduling overruns Nov 17 18:17:35 /kernel: vr0: rx packet lost Nov 17 18:17:31 /kernel: vr0: rx packet lost Nov 17 18:17:31 /kernel: usb0: 1 scheduling overruns Nov 17 18:15:08 /kernel: usb0: 1 scheduling overruns Nov 17 18:14:35 /kernel: vr0: rx packet lost Nov 17 18:14:34 /kernel: vr0: rx packet lost Nov 17 18:14:34 /kernel: usb0: 1 scheduling overruns Nov 17 18:13:56 /kernel: vr0: rx packet lost Nov 17 18:10:43 /kernel: vr0: rx packet lost Nov 17 18:10:43 /kernel: usb0: 1 scheduling overruns Nov 17 18:08:58 /kernel: vr0: rx packet lost Nov 17 18:08:58 /kernel: usb0: 1 scheduling overruns Nov 17 18:08:57 /kernel: vr0: rx packet lost Nov 17 18:08:57 /kernel: usb0: 1 scheduling overruns Nov 17 18:08:55 /kernel: vr0: rx packet lost Nov 17 18:08:55 /kernel: usb0: 1 scheduling overruns Nov 17 18:08:43 /kernel: vr0: rx packet lost Nov 17 18:08:43 /kernel: usb0: 1 scheduling overruns Nov 17 18:07:48 /kernel: vr0: rx packet lost Nov 17 18:07:48 /kernel: usb0: 1 scheduling overruns Our Soekris routers do have a usb interface but we don't use it. Does it need to be deactivated in the BIOS? To my knowledge nothing has changed in our configuration, so I don't understand why this is showing up now. Thank you in advance for your expertise :) Chris Dover NH, USA |