Printer stops mid-job; thereafter, USB mouse fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I am not sure, but I believe I have not printed anything since my install of Lubuntuy 16.10 last week.
I printed something from LibreOffice Calc, and it got only partway, and the printer stopped printing. I then noticed that the mouse (USB) had stopped working - I thought the batteries had co-incidentally failed, but fresh batteries accomplished nothing.
I had to shut down.
The next time, feeling that the print function of Calc was faulty, I exported the file as .pdf, and printed from Document Viewer (Evince). It got just about as far, and stopped, and the mouse failed again.
The next time, I was printing something from Firefox, and it got most of the way through that, but it stopped, and the mouse failed again.
By now, I had "installed" and activated PointerKeys, and with it, I was (slowly and painfully) able to have the terminal do lsusb and cut-n-paste the output to leafpad and save.
Some website suggested one could "reboot" the USB system, but I apparently failed to understand or apply the knowledge to success (or the procedure did not somehow apply to my current OS).
Rebooting sometimes (always?) does NOT fix the problem - Shutdown so far has.
When things are good, there are a lot more items in lsusb than when the mouse was not working.
When the mouse did not work:
scott@scott-
Bus 001 Device 006: ID 7392:7622 Edimax Technology Co., Ltd
Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
When the mouse works:
scott@scott-
Bus 001 Device 006: ID 7392:7622 Edimax Technology Co., Ltd
Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0a12:1004 Cambridge Silicon Radio, Ltd
Bus 002 Device 003: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
Bus 002 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 002 Device 002: ID 0a05:7211 Unknown Manufacturer hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Syslog shows some stuff that may show the problem happening:
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:32 scott-ASUS-
Oct 26 16:55:33 scott-ASUS-
Oct 26 16:55:33 scott-ASUS-
Oct 26 16:55:33 scott-ASUS-
Oct 26 16:55:33 scott-ASUS-
Oct 26 16:55:33 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:57:53 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
Oct 26 16:58:30 scott-ASUS-
"HC died; cleaning up" doesn't sound good, and all those USB devices disconnecting, makes sense, although I don't actually see a device 8 in my list from after shutting down (and not trying to print something).
1. Does anyone know why this is happening, and how to stop it?
2. I would not like to shutdown every time I lose the mouse - how should I re-boot the USB?
-Scott Jacobs
-------
scott@scott-
Linux scott-ASUS-
scott@scott-
Ubuntu 16.10
yakkety
scott@scott-
Lubuntu
cups (et al.): 2.2.0-2
cups-filters : 1.11.4-0ubuntu2
hplip(et al.): 3.16.7+
gtklp(et al.): 1.11.4-0ubuntu2
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cups 2.2.0-2
ProcVersionSign
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Oct 26 21:18:45 2016
InstallationDate: Installed on 2016-10-20 (7 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lpstat: device for HP-Deskjet-
MachineType: System manufacturer System Product Name
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1802
dmi.board.
dmi.board.name: M2N68-AM Plus
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
I still have not been able to complete a print job without the USB devices disconnecting.
Comment #22 of the "Duplicate bug" states:
"I was able to fix the issue by changing the IO_WATCHDOG_DELAY in ohci-hcd.c from 250 msec to 275 msec. "
Only once has this bug manifested when I was NOT trying to print something,
so I guess my question is: why does cups somehow generate an excessively long IO_WATCHDOG_DELAY
such that it always at some point in a print job trips the bug?
I know nothing about USB, or what IO_WATCHDOG_DELAY is, but I have 8 or 9 devices hooked up with USB, and (with the one exception noted above) only the printer has tripped this bug.
What is this delay used for, and why is cups' so large so often?
(In other words: the kernel may have a bug in how it handles IO_WATCHDOG_DELAY, but if cups did not generate a delay that tripped the bug, there would be no issue for printing. )