From: Tim Waugh <twaugh@redhat.com>
To: Juan <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: Tue, 10 Apr 2001 17:48:03 +0100 [thread overview]
Message-ID: <20010410174803.X1136@redhat.com> (raw)
In-Reply-To: <20010330152921.Q10553@redhat.com> <Pine.LNX.4.21.0103310156530.23634-100000@ditec.um.es> <20010403173839.I9355@redhat.com> <3ACA55D5.FC2E444C@ditec.um.es> <20010404092610.P9355@redhat.com> <3ACCDB0C.3A3ED66C@ditec.um.es>
In-Reply-To: <3ACCDB0C.3A3ED66C@ditec.um.es>; from piernas@ditec.um.es on Thu, Apr 05, 2001 at 10:52:28PM +0200
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
On Thu, Apr 05, 2001 at 10:52:28PM +0200, Juan wrote:
> Tim Waugh escribió:
> >
> > Could you build a kernel without SMP support and see if the problem
> > still happens?
> Without SMP support, the machine doesn't hang but I can't load the ppa
> module.
> See messages below.
[...]
> [root@localhost /root]# modprobe ppa
> ppa: Version 2.07 (for Linux 2.2.x)
> WARNING - no ppa compatible devices found.
> As of 31/Aug/1998 Iomega started shipping parallel
> port ZIP drives with a different interface which is
> supported by the imm (ZIP Plus) driver. If the
> cable is marked with "AutoDetect", this is what has
> happened.
> scsi : 0 hosts.
> /lib/modules/2.2.19/scsi/ppa.o: init_module: Device or resource busy
That's really strange. Does anyone else see this problem with ppa in
2.2.19? The only change should be to the _error_ path; it shouldn't
make things that once worked not work.
> > You could remove this line, just to see if it makes a difference (it
> > shouldn't, but it might).
> I will try this tomorrow.
I take it that it had no effect?
> > > messages on screen, doesn't it?
> >
> > Better is something like 'dmesg -n 8'.
> OK.
How about this? Did you see messages on the screen on the SMP kernel
with 'dmesg -n 8' set when you load ppa?
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-04-10 16:48 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
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 [this message]
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=20010410174803.X1136@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 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.