From: Pete Zaitcev <zaitcev@redhat.com>
To: pete.lkml@toscano.org, linux-kernel@vger.kernel.org
Subject: Re: USB printing == kernel lockup?
Date: Tue, 3 Jul 2001 20:33:12 -0400 [thread overview]
Message-ID: <200107040033.f640XCP18378@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.994200601.27241.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.994200601.27241.linux-kernel2news@redhat.com>
> When I do anything (print to it, query its ink levels with escputil,
> etc.) with my Epson 870 while it's hooked to my computer via USB, the
> whole machine locks hard. [...]
> Has anyone else has seen this problem? I posted to the gimp-print and
> linux-usb lists, but there was nary a response.
I think I saw your message, but very little can be extracted
from that data.
-- Pete
next parent reply other threads:[~2001-07-04 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.994200601.27241.linux-kernel2news@redhat.com>
2001-07-04 0:33 ` Pete Zaitcev [this message]
2001-07-03 22:47 USB printing == kernel lockup? Pete Toscano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107040033.f640XCP18378@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pete.lkml@toscano.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.