From: Tim Waugh <twaugh@redhat.com>
To: Juan Piernas Canovas <piernas@ditec.um.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 && ppa: total lockup. No problem with 2.2.17
Date: Fri, 30 Mar 2001 15:29:21 +0100 [thread overview]
Message-ID: <20010330152921.Q10553@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103301519370.13429@ditec.um.es> <Pine.LNX.4.21.0103301554310.14247-100000@ditec.um.es>
In-Reply-To: <Pine.LNX.4.21.0103301554310.14247-100000@ditec.um.es>; from piernas@ditec.um.es on Fri, Mar 30, 2001 at 03:55:01PM +0200
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Fri, Mar 30, 2001 at 03:55:01PM +0200, Juan Piernas Canovas wrote:
> The kernel configuration is the same in both 2.2.17 and 2.2.19.
> Perhaps, the problem is not in the ppa module, but in the parport,
> parport_pc or parport_probe modules.
There weren't any parport changes in 2.2.18->2.2.19, and the ones in
2.2.17->2.2.18 won't affect you unless you are using a PCI card.
Could you please try this patch and let me know if the behaviour
changes?
Thanks,
Tim.
*/
--- linux/drivers/scsi/ppa.h.eh Fri Mar 30 15:27:43 2001
+++ linux/drivers/scsi/ppa.h Fri Mar 30 15:27:52 2001
@@ -178,7 +178,6 @@
eh_device_reset_handler: NULL, \
eh_bus_reset_handler: ppa_reset, \
eh_host_reset_handler: ppa_reset, \
- use_new_eh_code: 1, \
bios_param: ppa_biosparam, \
this_id: -1, \
sg_tablesize: SG_ALL, \
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-03-30 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0103301519370.13429@ditec.um.es>
2001-03-30 13:55 ` 2.2.19 && ppa: total lockup. No problem with 2.2.17 Juan Piernas Canovas
2001-03-30 14:29 ` Tim Waugh [this message]
2001-03-30 23:59 ` [SOLVED]Re: " Juan Piernas Canovas
2001-04-03 16:38 ` Tim Waugh
2001-04-03 22:59 ` Juan
2001-04-04 8:26 ` Tim Waugh
2001-04-05 20:52 ` Juan
2001-04-10 16:48 ` Tim Waugh
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=20010330152921.Q10553@redhat.com \
--to=twaugh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piernas@ditec.um.es \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox