From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] parport_pc: after superio probing restore original register values
Date: Mon, 22 Jun 2009 11:41:57 -0400 [thread overview]
Message-ID: <4A3FA645.8020701@garzik.org> (raw)
In-Reply-To: <20090622155142.17809.75363.stgit@t61.ukuu.org.uk>
Alan Cox wrote:
> From: Jens Rottmann <JRottmann@LiPPERTEmbedded.de>
>
> CONFIG_PARPORT_PC_SUPERIO probes for various superio chips by writing
> byte sequences to a set of different potential I/O ranges. But the
> probed ranges are not exclusive to parallel ports. Some of our boards
> just happen to have a watchdog in one of them. Took us almost a week
> to figure out why some distros reboot without warning after running
> flawlessly for 3 hours. For exactly 170 = 0xAA minutes, that is ...
>
> Fixed by restoring original values after probing. Also fixed too small
> request_region() in detect_and_report_it87().
>
> Signed-off-by: Jens Rottmann <JRottmann@LiPPERTEmbedded.de>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> Cc: <stable@kernel.org>
> ---
>
> drivers/parport/parport_pc.c | 31 +++++++++++++++++++++++++------
> 1 files changed, 25 insertions(+), 6 deletions(-)
Acked-by: Jeff Garzik <jgarzik@redhat.com>
next prev parent reply other threads:[~2009-06-22 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 15:47 [PATCH 0/2] Parallel port fixes for 2.6.31 Alan Cox
2009-06-22 15:51 ` [PATCH 1/2] parport_pc: after superio probing restore original register values Alan Cox
2009-06-22 15:41 ` Jeff Garzik [this message]
2009-06-22 15:54 ` [PATCH 2/2] parport_pc: set properly the dma_mask for parport_pc device Alan Cox
2009-06-22 15:42 ` Jeff Garzik
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=4A3FA645.8020701@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.