public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan <piernas@ditec.um.es>
To: Tim Waugh <twaugh@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [SOLVED]Re: 2.2.19 && ppa: total lockup. No problem with 2.2.17
Date: Wed, 04 Apr 2001 00:59:33 +0200	[thread overview]
Message-ID: <3ACA55D5.FC2E444C@ditec.um.es> (raw)
In-Reply-To: <20010330152921.Q10553@redhat.com> <Pine.LNX.4.21.0103310156530.23634-100000@ditec.um.es> <20010403173839.I9355@redhat.com>

Tim Waugh escribió:
> 
> 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.
Right

> 
> Are you using any special parport/ppa parameters?  Is this an SMP or a
> uniprocessor machine?  Come to that, which architecture is it?
> 
I have the same problem in two different machines but they both are UP.
However, my kernel configuration has SMP support enabled.

My modules.conf file is:

alias scsi_hostadapter ppa
alias parport_lowlevel parport_pc
options parport_pc io=0x378 irq=7


> 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.

I stop klogd and syslogd services (that causes to display all kernel
messages on screen, doesn't it? and, when I load the ppa modules, the
machine simply hangs: no messages, no sysreq key anymore.

Bye!

	Juan.

-- 
D. Juan Piernas Cánovas
Departamento de Ingeniería y Tecnología de Computadores
Facultad de Informática. Universidad de Murcia
Campus de Espinardo - 30080 Murcia (SPAIN)
Tel.: +34968367657    Fax: +34968364151
email: piernas@ditec.um.es
PGP public key:
http://pgp.rediris.es:11371/pks/lookup?search=piernas%40ditec.um.es&op=index

  reply	other threads:[~2001-04-03 22: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
2001-04-03 22:59         ` Juan [this message]
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=3ACA55D5.FC2E444C@ditec.um.es \
    --to=piernas@ditec.um.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.com \
    /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