mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Nigel Kukard <nkukard@lbsd.net>,
	Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: 2.6.9bk6 msdos fs OOPS
Date: Thu, 28 Oct 2004 07:59:28 -0400	[thread overview]
Message-ID: <200410280759.28282.gene.heskett@verizon.net> (raw)
In-Reply-To: <200410280714.40033.gene.heskett@verizon.net>

On Thursday 28 October 2004 07:14, Gene Heskett wrote:
>On Thursday 28 October 2004 05:23, OGAWA Hirofumi wrote:
>>Nigel Kukard <nkukard@lbsd.net> writes:
>>> OOPS is 100% reproducable. I boot into X, and run    eog
>>> /mnt/camera/dcim/100cresi    and BANG.
>>
>>This is known problem. Can you please try the following patch?
>>Then, please send debugging output.
>>
>>Thanks.
>
>This still applies cleanly to 2.6.10-rc1-bk6, so I'm building it to
>test also.  I have an Olympus C-3020 that mounts as a vfat file
>system over usb.  It has been somewhat of a problem if the card has
>quite a few pix on it, I must copy, and delete, from the bottom of
>the dirlisting else it goes read-only on me.  When the build is
> done, I'll try mounting it to see if this also gives an Oops, then
> reboot and try again, and report the results.

OGAWA;  I didn't notice I wasn't running gnome, but use kde.  I have 
been able to mount, read the empty card in it, and unmount it 3 times 
with no Oops with the unpatched 2.6.10-rc1-bk6 kernel.  Now I'll 
reboot and retest tour patch.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.28% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

  reply	other threads:[~2004-10-28 12:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28  7:00 Nigel Kukard
2004-10-28  7:55 ` Denis Vlasenko
2004-10-28  8:11   ` Nigel Kukard
2004-10-28  9:23     ` OGAWA Hirofumi
2004-10-28 10:50       ` Nigel Kukard
2004-10-28 13:18         ` OGAWA Hirofumi
2004-10-28 11:14       ` Gene Heskett
2004-10-28 11:59         ` Gene Heskett [this message]
2004-10-28 12:12         ` Gene Heskett
2004-10-28 13:21           ` OGAWA Hirofumi
2004-10-28 15:24             ` Nigel Kukard
2004-10-28 15:58               ` OGAWA Hirofumi
2004-10-28 18:32               ` Gene Heskett
2004-10-28 18:32             ` Gene Heskett
2004-10-28 19:50               ` OGAWA Hirofumi
2004-10-28 23:05                 ` Gene Heskett
2004-10-29  0:01                   ` OGAWA Hirofumi
2004-10-29  4:50                     ` Gene Heskett
2004-10-29  5:31                       ` Gene Heskett
2004-10-28  8:21 ` Al Viro

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=200410280759.28282.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkukard@lbsd.net \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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

all inboxes | Powered by JetHome®