public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Detlev Offenbach <detlev@offenbach.fs.uunet.de>
To: linux-kernel@vger.kernel.org
Subject: MO-Drive under 2.4.7 usinf vfat
Date: Sat, 21 Jul 2001 15:26:58 +0200	[thread overview]
Message-ID: <01072115265800.02284@majestix> (raw)

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

Hi all,

I have just tested the new 2.4.7 kernel to see, whether it now works with a 
MO-Drive using the vfat filesystem. Unfortunately it still doesn't. Mounting 
a disk and writing to it is ok. However, when I try to read a file off the 
disk, the program crashes with a Segmentation fault and I get a oops in the 
messages file (see attachment). I tried ksymoops on this file, but either I 
did something wrong or it couldn't analyse it.

I hope, this issue will be fixed soon cause I would like to switch over to 
the 2.4 kernel series without scratching my set of MO-disks.

Regards
Detlev

Btw, please answer by email as well because I think I got removed from the 
mailing list somehow (or is it that quiet?).
-- 
Detlev Offenbach
detlev@offenbach.fs.uunet.de

[-- Attachment #2: oops.txt --]
[-- Type: text/plain, Size: 1290 bytes --]

Jul 21 14:38:21 majestix kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Jul 21 14:38:21 majestix kernel:  printing eip:
Jul 21 14:38:21 majestix kernel: 00000000
Jul 21 14:38:21 majestix kernel: *pde = 00000000
Jul 21 14:38:21 majestix kernel: Oops: 0000
Jul 21 14:38:21 majestix kernel: CPU:    0
Jul 21 14:38:21 majestix kernel: EIP:    0010:[<00000000>]
Jul 21 14:38:21 majestix kernel: EFLAGS: 00010282
Jul 21 14:38:21 majestix kernel: eax: 00000000   ebx: d729dcc0   ecx: 00004000   edx: d729dce0
Jul 21 14:38:21 majestix kernel: esi: 40017000   edi: 00000000   ebp: 00004000   esp: d727ff80
Jul 21 14:38:21 majestix kernel: ds: 0018   es: 0018   ss: 0018
Jul 21 14:38:21 majestix kernel: Process more (pid: 1191, stackpage=d727f000)
Jul 21 14:38:21 majestix kernel: Stack: e2bad8fd d729dcc0 40017000 00004000 d729dce0 d729dcc0 ffffffea c012e156 
Jul 21 14:38:21 majestix kernel:        d729dcc0 40017000 00004000 d729dce0 d727e000 08050b68 08050b68 bffff49c 
Jul 21 14:38:21 majestix kernel:        c0106c2b 00000003 40017000 00004000 08050b68 08050b68 bffff49c 00000003 
Jul 21 14:38:21 majestix kernel: Call Trace: [sys_read+150/208] [system_call+51/56] 
Jul 21 14:38:21 majestix kernel: 
Jul 21 14:38:21 majestix kernel: Code:  Bad EIP value.

             reply	other threads:[~2001-07-21 13:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-21 13:26 Detlev Offenbach [this message]
2001-07-21 16:17 ` MO-Drive under 2.4.7 usinf vfat Steven Walter
2001-07-21 16:30   ` kgdb and/or kdb for RH7.1 Michael S. Miles
2001-07-21 19:16     ` Tigran Aivazian
2001-07-23  8:44       ` Amit S. Kale
2001-07-21 19:58     ` arjan
2001-07-22  1:58     ` Keith Owens
2001-07-22  3:09       ` Keith Owens
2001-07-22 14:07 ` MO-Drive under 2.4.7 usinf vfat OGAWA Hirofumi
2001-07-23 13:38 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2001-07-21 16:15 Douglas Gilbert
2001-07-22 14:49 Douglas Gilbert
2001-07-22 17:47 ` OGAWA Hirofumi
2001-07-24  8:33 ` Jens Axboe
2001-07-24 17:00   ` Alan Cox
2001-07-24 17:50     ` OGAWA Hirofumi
2001-07-25  6:35     ` 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=01072115265800.02284@majestix \
    --to=detlev@offenbach.fs.uunet.de \
    --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