Hi Rik Rik Griffin wrote:
About a year (almost exactly) I discovered a problem with the EtherK module 0.18 that caused the IRQ in use by the network device to fail after a period of intensive use. I think Gary Locock found the same problem as a result of heavy use of ShareFS. Castle tracked down the problem to the EtherK module, and version 0.19 was released which seemed to cure the problem However the same problem has resurfaced for me, a year later, the difference being that I'm now making even heavier use of the network interface (3-4 MBits per second, constantly 24 hours a day). After about 20 hours of this, something goes wrong and the ethernet device's IRQ (59) is disabled. Anything else using that IRQ of course stops working too (eg one of the USB channels) Reenabling the IRQ restores function to the affected devices. So, has anyone else seen this problem recently?
no.. not here
And a question to John - I'm still using RO5.11 with EtherK 0.19. Are thereany fixes that might help in 5.12?
not intentionally I'm afraid.Might I suggest moving the usb to another pci slot .. and checking whether the issue stays in the n/w irq, or moves with the usb (same or different usb channel blocked)? .. just to isolate the issue to the n/w only?
Thanks
Am I right in saying all new machines come with 5.12? If so I should upgrade my dev machine anyway.
if you can grab one of your recent delivery, that is ro512.. worth double checking with.
do phone to discuss John
-- John Ballance jwb@xxxxxxxxxx http://www.rosery.net http://www.johnballance.co.uk ---To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support
Other info via //www.freelists.org/webpage/iyonix-support