All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raphael Assenat <raph@raphnet.net>
To: sparclinux@vger.kernel.org
Subject: Re: Parallel port problems on Sun Ultra10
Date: Mon, 10 Apr 2006 01:10:11 +0000	[thread overview]
Message-ID: <20060410011011.GA22569@aramis.lan.raphnet.net> (raw)
In-Reply-To: <1144596830.4439295e52873@imp1-g19.free.fr>

On Sun, Apr 09, 2006 at 05:33:50PM +0200, Christophe Jacquet wrote:
> When I type " echo 'Hello world' >/dev/lp0 ", I get the message:
> 
> lp0: ECP mode
> 
> The string gets printed on the printer.
> 
> Then, Linux crashes. I get no more messages. The Bash prompt never comes back. I
> can interact with OBP by hitting "Stop-A", and reboot the machine.
Hi,
this reminds me of a problem I had a few week ago while playing with
an homebuild parallel port project. The machine would lock totally, but
as soon as I disconnected the circuit from the port the machine would
unlock. 

Maybe you could try disconnecting the printer and see what happens?

Here are more details about the problem I observed:

When the parallel port interrupt is enabled, the machine hangs as long as
the ACK pin is held low. I observed that the parport interrupt count in
/proc/interrupt were higher after each hang. 

It looks to me like the parport interrupt is level triggered instead 
of edge triggered. I wanted try on x86 hardware to see if the problem
also happens before posting, but I decided to post anyway when I saw
this message.

I observed this on a 2.6.16-rc6-git-something.

Regards,
Raphael Assenat

  reply	other threads:[~2006-04-10  1:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 15:33 Parallel port problems on Sun Ultra10 Christophe Jacquet
2006-04-10  1:10 ` Raphael Assenat [this message]
2006-04-10  9:11 ` Christophe Jacquet
2006-04-10 15:36 ` Christophe Jacquet
2006-04-10 23:14 ` David S. Miller
2006-04-11  2:01 ` Jurij Smakov

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=20060410011011.GA22569@aramis.lan.raphnet.net \
    --to=raph@raphnet.net \
    --cc=sparclinux@vger.kernel.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.