http://bugzilla.novell.com/show_bug.cgi?id=562282
http://bugzilla.novell.com/show_bug.cgi?id=562282#c5
--- Comment #5 from Johannes Meixner 2009-12-15 08:41:07 UTC ---
To analyze what in "lpinfo -v" lets the system freeze:
Basically "lpinfo -v" lets the cupsd launch the cups-deviced, see
http://www.cups.org/documentation.php/doc-1.3/man-cups-deviced.html
which calls each executable file in /usr/lib/cups/backend
without parameters.
When a CUPS backenmd is called without parameters, it does
autodetection, see "man 7 backend".
I assume one of those backends lets the system freeze
when it does autodetection.
I guess it is the parallel or usb backend.
As root call each executable file in /usr/lib/cups/backend
until you found the one which lets your system freeze.
Usually it works as follows:
root@host# /usr/lib/cups/backend/usb
direct usb://HP/LaserJet%201100
root@host# /usr/lib/cups/backend/parallel
direct parallel:/dev/lp0
In particular reagrding the parallel port:
Note that wrong parport_pc settings in /etc/modprobe.conf
(i.e. settings which do not match to your actual hardware)
can cause the kernel to freeze because those settings
are direct hardware settings (DMA, IO-port, interrupt)
and wrong hardware settings can of course let the system freeze.
But again I have no knowledge at all about how to find out
what the right parallel port hardware settings are
in case of a docking station.
For a usual PC the settings must match to what is set
in the BIOS of the PC.
But does a docking station have a BIOS where the user
can read and change its values?
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.