https://bugzilla.novell.com/show_bug.cgi?id=751712
https://bugzilla.novell.com/show_bug.cgi?id=751712#c10
Wolfgang Rosenauer changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #10 from Wolfgang Rosenauer 2012-03-15 06:31:14 UTC ---
USB kernel developers found the issue:
"
Okay, I see what the problem is. Your printer has a mass-storage
interface -- a card reader or something of the sort, right?
Starting in 3.1 the kernel continually polls this mass-storage
interface, looking for media-change events (such as insertion of a
memory card). Right at the time you began printing, the mass-storage
interface stopped responding to these polls. After 30 seconds the
computer realized something was wrong, so it reset the printer. This
reset interfered with the printing, so the second page never got
completed.
If you don't care about that card reader or whatever it is, you can
prevent the kernel from polling it. The command to use is:
echo 0 >/sys/block/sdX/events_poll_msecs
where the X has to be filled in with the appropriate drive letter.
You can see what the drive letter is by looking in the system log for
the time when the printer was plugged in or turned on.
With a little effort you could even write a udev rule that would do
this for you automatically every time the printer is connected.
"
I can confirm that the printer has a builtin card reader (which I do not use
usually) and disabling the poll makes printing work reliably.
I'm wondering if there is no solution available to make it just work somehow?
This sounds like an issue which could not only happen to me.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.