public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: 2.5.67: ppa driver & preempt == oops
Date: Tue, 15 Apr 2003 20:30:34 -0700	[thread overview]
Message-ID: <3E9CCE5A.30708@myrealbox.com> (raw)
In-Reply-To: <20030415162515.A362@beaverton.ibm.com>

Patrick Mansfield wrote:
> On Tue, Apr 15, 2003 at 04:04:02PM -0700, walt wrote:
> 
> 
>>Yes!  Thank you.  This patch fixes the segfault of modprobe that I've 
>>been seeing for ages.
>>
>>Note that the problems I have been seeing are completely different from 
>>Geert's problems.  I have had no problems mounting a FAT-16 fs with the 
>>2.5.x kernels but modprobe has been segfaulting all along, even though 
>>the ppa module works fine for me once it has been loaded.
> 
> 
> The other problem seems to be for removable media. Is your parallel zip
> have removable media and does the boot/dmesg output from sd attach show it
> as such? I haven't used a zip drive, I thought they had to be marked
> removable.

Seems to be:

ppa: Version 2.07 (for Linux 2.4.x)
ppa: Found device at ID 6, Attempting to use EPP 32 bit
ppa: Found device at ID 6, Attempting to use SPP
ppa: Communication established with ID 6 using SPP
scsi0 : Iomega VPI0 (ppa) interface
   Vendor: IOMEGA    Model: ZIP 100           Rev: C.18
   Type:   Direct-Access                      ANSI SCSI revision: 02
SCSI device sda: 196608 512-byte hdwr sectors (101 MB)
sda: Write Protect is off
sda: Mode Sense: 25 00 00 08
sda: cache data unavailable
sda: assuming drive cache: write through
  /dev/scsi/host0/bus0/target6/lun0: p4
Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0
               ^^^^^^^^^


  reply	other threads:[~2003-04-16  3:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.chdor2j.u72387@ifi.uio.no>
     [not found] ` <fa.gs8uudl.196640l@ifi.uio.no>
2003-04-15 23:04   ` [PATCH] Re: 2.5.67: ppa driver & preempt == oops walt
2003-04-15 23:25     ` Patrick Mansfield
2003-04-16  3:30       ` walt [this message]
     [not found] <fa.cde0mrb.127uv05@ifi.uio.no>
     [not found] ` <fa.i9on98t.1gg0toj@ifi.uio.no>
2003-04-17 19:37   ` walt
2003-04-16  9:45 Chuck Ebbert
     [not found] <fa.fo1ils5.o4kt21@ifi.uio.no>
     [not found] ` <fa.jt2b7k8.20qj0c@ifi.uio.no>
2003-04-16  3:19   ` walt
     [not found] <fa.hdvi4hc.152sj34@ifi.uio.no>
     [not found] ` <fa.fnhqqrs.ok0028@ifi.uio.no>
2003-04-15 23:51   ` walt
2003-04-16  0:07     ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
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-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

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=3E9CCE5A.30708@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