linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.67: ppa driver & preempt == oops
Date: Sun, 13 Apr 2003 12:52:33 -0700	[thread overview]
Message-ID: <3E99C001.7030209@myrealbox.com> (raw)
In-Reply-To: <fa.h6rb9ej.ml8qhn@ifi.uio.no>

Andrew Morton wrote:
> Gert Vervoort <gert.vervoort@hccnet.nl> wrote:
> 
>>ppa: Version 2.07 (for Linux 2.4.x)
>>ppa: Found device at ID 6, Attempting to use EPP 16 bit
>>ppa: Communication established with ID 6 using EPP 16 bit
>>scsi0 : Iomega VPI0 (ppa) interface
>>bad: scheduling while atomic!
> 
> 
> This patch should make the warnings go away.
> 
> I've been sitting on it for a while, waiting for someone to tell me if the
> ppa driver actually works.  Perhaps that person is you?

I've responded to your questions more than once but evidently you
haven't seen or been able to parse my responses.

To recap:  I see a non-fatal kernel-oops and modprobe segfaults after
successfully loading the ppa module.  Once the ppa module is loaded the
ppa driver actually does work with 2.5.x for at least x>50 (I haven't 
tried x<50).

I am using preemptable kernel and devfs and I do NOT see any of the
warnings that Geert is seeing.  The only problems I see with Linus's
2.5.x kernels is the segfault by modprobe, not with the function of
ppa itself.

What definitely confused me for a long time is that the -ac series
doesn't work with devfs+ppa because the scsi ppa device never
shows up in /dev -- but I think that has nothing to do with Geert's
problem or with your question either, just an aside to explain why
my previous posts may have been confusing the issue.

BTW, the parallel Zip drive is the only SCSI device I have.  Would
my kernel config file be of any use to you?


       reply	other threads:[~2003-04-13 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.e0puan3.1f34a3p@ifi.uio.no>
     [not found] ` <fa.h6rb9ej.ml8qhn@ifi.uio.no>
2003-04-13 19:52   ` walt [this message]
     [not found] <20030413201011$1026@gated-at.bofh.it>
     [not found] ` <20030413201011$250d@gated-at.bofh.it>
     [not found]   ` <20030413201011$5dde@gated-at.bofh.it>
2003-04-14  4:17     ` 2.5.67: ppa driver & preempt == oops Tim Connors
2003-04-12 15:03 Gert Vervoort
2003-04-12 18:28 ` Robert Love
2003-04-13 10:30   ` Gert Vervoort
2003-04-13 17:32     ` Robert Love
2003-04-13 17:44       ` Gert Vervoort
2003-04-12 21:12 ` Andrew Morton
2003-04-13 11:45   ` Gert Vervoort
2003-04-13 20:44     ` Andrew Morton

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=3E99C001.7030209@myrealbox.com \
    --to=wa1ter@myrealbox.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).