All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gert Vervoort <gert.vervoort@hccnet.nl>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: tconnors@astro.swin.edu.au, Robert Love <rml@tech9.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: 2.5.67: ppa driver & preempt == oops
Date: Tue, 15 Apr 2003 22:44:00 +0200	[thread overview]
Message-ID: <3E9C6F10.10001@hccnet.nl> (raw)
In-Reply-To: 20030415120000.A30422@beaverton.ibm.com

Patrick Mansfield wrote:

>On Sun, Apr 13, 2003 at 07:44:04PM +0200, Gert Vervoort wrote:
>
>Here is a patch against 2.5.67, can you try it out?
>
>I did not compile let alone run with this patch.
>  
>
The patch compiles and the warning messages are gone now.
But, I still can't mount a zip disk.

Kernel messages after mounting a zip disk (mount -t ext2 /dev/sda1 
/mnt/zip):

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
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
 sda:

The kernel messages are showing twice, does it try to mount the zip disk 
two times?

At this point the mount process is stuck:

[root@viper root]# ps -ax | grep zip
  998 tty1     D      0:00 mount -t ext2 /dev/sda1 /mnt/zip
 1057 tty2     S      0:00 grep zip
[gert@viper root]$


    Gert





  reply	other threads:[~2003-04-15 20:30 UTC|newest]

Thread overview: 29+ 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
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 [this message]
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.chdor2j.u72387@ifi.uio.no>
     [not found] ` <fa.gs8uudl.196640l@ifi.uio.no>
2003-04-15 23:04   ` [PATCH] " walt
2003-04-15 23:25     ` Patrick Mansfield
2003-04-16  3:30       ` 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
     [not found] <fa.fo1ils5.o4kt21@ifi.uio.no>
     [not found] ` <fa.jt2b7k8.20qj0c@ifi.uio.no>
2003-04-16  3:19   ` walt
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16  9:45 Chuck Ebbert
     [not found] <fa.cde0mrb.127uv05@ifi.uio.no>
     [not found] ` <fa.i9on98t.1gg0toj@ifi.uio.no>
2003-04-17 19:37   ` walt

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=3E9C6F10.10001@hccnet.nl \
    --to=gert.vervoort@hccnet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patmans@us.ibm.com \
    --cc=rml@tech9.net \
    --cc=tconnors@astro.swin.edu.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.