From: Tim Waugh <twaugh@redhat.com>
To: Juan Piernas Canovas <piernas@ditec.um.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [SOLVED]Re: 2.2.19 && ppa: total lockup. No problem with 2.2.17
Date: Tue, 3 Apr 2001 17:38:39 +0100 [thread overview]
Message-ID: <20010403173839.I9355@redhat.com> (raw)
In-Reply-To: <20010330152921.Q10553@redhat.com> <Pine.LNX.4.21.0103310156530.23634-100000@ditec.um.es>
In-Reply-To: <Pine.LNX.4.21.0103310156530.23634-100000@ditec.um.es>; from piernas@ditec.um.es on Sat, Mar 31, 2001 at 01:59:39AM +0200
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Sat, Mar 31, 2001 at 01:59:39AM +0200, Juan Piernas Canovas wrote:
> Yes!!!. It works. I am happy now :-)
Unfortunately, the problem isn't solved, merely worked around. We
need to figure out why this is happening in the first place.
To recap, the system hangs completely when you load the ppa module.
Are you using any special parport/ppa parameters? Is this an SMP or a
uniprocessor machine? Come to that, which architecture is it?
Are there any messages displayed to the console when the hang happens?
If you could scatter some printks around (KERN_CRIT so they show up on
the console) to figure out the example point at which it's hanging,
that would be great.
Thanks,
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-04-03 16:39 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 [this message]
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=20010403173839.I9355@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