OHCI-PCI: frame counter not updating, module disabled
This happens also with older kernel versions (3.x, etc.): A small LCD display (ID 1908:0102 GEMBIRD) connected to USB is used for some years now. Computer (and display) runs always (24 hours/day). 'lcd4linux' is used to update the displays contents. This works fine - but it fails after 1-2 days. The log shows: ohci-pci :00:12.0: frame counter not updating; disabled ohci-pci :00:12.0: HC died; cleaning up The ohci-pci module will be disabled then, the display gets lost. A workaround for this is to reload this module every 24 hours (automated by a systemd service). So far this helps: I didn't have this error anymore. This workaround is tested for a few months now and it runs fine - but it's 'only' a workaround. ;) > On Wed, Feb 17, 2016 at 02:50:45AM +, bugzilla-dae...@bugzilla.kernel.org wrote: > Please send to the linux-usb@vger.kernel.org mailing list. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OHCI-PCI: frame counter not updating, module disabled
On Thu, 18 Feb 2016 m...@superbash.de wrote: > This happens also with older kernel versions (3.x, etc.): > > A small LCD display (ID 1908:0102 GEMBIRD) connected to USB is used for > some years now. Computer (and display) runs always (24 hours/day). > 'lcd4linux' is used to update the displays contents. > > This works fine - but it fails after 1-2 days. > > The log shows: > > ohci-pci :00:12.0: frame counter not updating; disabled > ohci-pci :00:12.0: HC died; cleaning up > > The ohci-pci module will be disabled then, the display gets lost. That error message indicates a problem in the OHCI hardware. I don't what causes the problem or how to prevent it. > A workaround for this is to reload this module every 24 hours > (automated by a systemd service). So far this helps: I didn't have this > error anymore. This workaround is tested for a few months now and it > runs fine - but it's 'only' a workaround. ;) That's okay. Reinitializing the controller and the driver is a perfectly reasonable workaround for a hardware problem. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
