public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Gert Vervoort <gert.vervoort@hccnet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67: ppa driver & preempt == oops
Date: 12 Apr 2003 14:28:03 -0400	[thread overview]
Message-ID: <1050172083.2291.459.camel@localhost> (raw)
In-Reply-To: <3E982AAC.3060606@hccnet.nl>

On Sat, 2003-04-12 at 11:03, Gert Vervoort 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

I guess you don't see these without kernel preemption?

These are not errors, just warnings.  Most likely you only see them when
CONFIG_PREEMPT is enabled, because otherwise the kernel cannot detect
them.  But they still happen.

Does anything go wrong?  Or just these errors?

It looks like one of the scsi command functions grabs a lock and then
does wait_for_completion.  I have not identified what lock, yet.  But
its a bug in the SCSI code if so, and unrelated to preemption.

	Robert Love


  reply	other threads:[~2003-04-12 18:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 15:03 2.5.67: ppa driver & preempt == oops Gert Vervoort
2003-04-12 18:28 ` Robert Love [this message]
2003-04-13 10:30   ` Gert Vervoort
2003-04-13 17:32     ` Robert Love
2003-04-13 17:44       ` Gert Vervoort
2003-04-15 19:00         ` [PATCH] " Patrick Mansfield
2003-04-15 20:44           ` Gert Vervoort
2003-04-15 21:40             ` Patrick Mansfield
2003-04-16 17:52               ` Gert Vervoort
2003-04-16 18:05                 ` Patrick Mansfield
2003-04-16 19:45                   ` Gert Vervoort
2003-04-16 20:07                     ` Mike Anderson
2003-04-16 18:03               ` Gert Vervoort
2003-04-15 21:37           ` Robert Love
2003-04-15 21:51             ` Randy.Dunlap
2003-04-15 22:07               ` Patrick Mansfield
2003-04-15 22:29                 ` Randy.Dunlap
2003-04-15 22:35                   ` Patrick Mansfield
2003-04-12 21:12 ` Andrew Morton
2003-04-13 11:45   ` Gert Vervoort
2003-04-13 20:44     ` Andrew Morton
     [not found] <fa.e0puan3.1f34a3p@ifi.uio.no>
     [not found] ` <fa.h6rb9ej.ml8qhn@ifi.uio.no>
2003-04-13 19:52   ` walt
     [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     ` Tim Connors

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=1050172083.2291.459.camel@localhost \
    --to=rml@tech9.net \
    --cc=gert.vervoort@hccnet.nl \
    --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