linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arthur Pedyczak <arthur-p@home.com>
To: Aaron Lunansky <alunansky@rim.net>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: loop problems continue in 2.4.3
Date: Sat, 14 Apr 2001 16:15:43 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0104141612250.27637-100000@cs865114-a.amp.dhs.org> (raw)
In-Reply-To: <A9FD1B186B99D4119BCC00D0B75B4D8107F45B05@xch01ykf.rim.net>

On Sat, 14 Apr 2001, Aaron Lunansky wrote:
Why not indeed? - should have thought about it myself

Well, I wrote the script. It has been running for 10 minutes now mounting
and unmounting an iso image. Nothing happens.
I guess I should be happy.
Still don't undertand where the original Oops
came
from

> If you're intent on making it oops why not write a script to
mount/unmount
> it repeatedly?
>
>
> Regards,
> Aaron
>
>
> -----Original Message-----
> From: Arthur Pedyczak <arthur-p@home.com>
> To: Jens Axboe <axboe@suse.de>
> CC: Linux kernel list <linux-kernel@vger.kernel.org>; Jeff Garzik
> <jgarzik@mandrakesoft.com>
> Sent: Sat Apr 14 08:46:49 2001
> Subject: Re: loop problems continue in 2.4.3
>
> On Sat, 14 Apr 2001, Jens Axboe wrote:
>
> [ SNIP..................]
> > > =====================
> > > Apr 13 20:50:03 cs865114-a kernel: Unable to handle kernel paging
> request at virtual address 7e92bfd7
> >
> > Please disable syslog decoding (it sucks) and feed it through ksymoops
> > instead.
> >
> > In other words, reproduce and dmesg | ksymoops instead.
> >
> >
> I tried to reproduce the error this morning and couldn't. Same kernel
> (2.4.3), same setup, same iso file. It mounted/unmounted 10 times with no
> problem. DOn't know what to think.
>
> Arthur
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2001-04-14 20:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-14 16:31 loop problems continue in 2.4.3 Aaron Lunansky
2001-04-14 20:15 ` Arthur Pedyczak [this message]
2001-04-16 23:02   ` David Woodhouse
     [not found] <3AD7EE80.5AADA578@mandrakesoft.com>
2001-04-16  1:08 ` Arthur Pedyczak
2001-04-16  1:37   ` Arthur Pedyczak
2001-04-16  8:49   ` Jens Axboe
2001-04-16  9:30     ` Alexander Viro
2001-04-16 10:10       ` Mircea Damian
2001-04-16 16:38         ` Jens Axboe
2001-04-16 16:37       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2001-04-14  3:35 Arthur Pedyczak
2001-04-14  7:54 ` Jens Axboe
2001-04-14 12:46   ` Arthur Pedyczak
2001-04-14 12:58     ` Ola Garstad
2001-04-07 22:04 Ian Eure
2001-04-09  7:56 ` Jens Axboe
2001-04-11 19:04 ` Ian Eure
2001-04-13 12:56   ` Jens Axboe
2001-04-16 16:17   ` Ian Eure
2001-04-16 20:53     ` Jens Axboe

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=Pine.LNX.4.33.0104141612250.27637-100000@cs865114-a.amp.dhs.org \
    --to=arthur-p@home.com \
    --cc=alunansky@rim.net \
    --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).