public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nick Ivanter <nick@auriga.ru>
To: dwmw2@infradead.org
Cc: mtd@infradead.org, jffs-dev@axis.com
Subject: Re: garbage collect
Date: Wed, 21 Jun 2000 12:06:05 +0400	[thread overview]
Message-ID: <3950776D.30AC4B13@auriga.ru> (raw)
In-Reply-To: Pine.LNX.4.10.10006201614120.7301-100000@impact-pc01.gnk.internal

dwmw2@infradead.org wrote:

> On Tue, 20 Jun 2000, Nick Ivanter wrote:
>
> > I've compiled JFFS and MTD into the kernel and tried to play with it on
> > the mtdram device. It seems to work, but when I tried to mount device
> > without manually specifying a filesystem type, I got error: "Unable to
> > handle kernel NULL pointer dereference at virtual address ...........
> > Process mount........... Segmentation fault". When specifying -t jffs,
> > everything seems to be ok.
> > Does anyone have ideas about what may cause that?
>
> Probably the mtdblock device falling over when a 'real' filesystem
> actually causes a block read request, which jffs will never do because it
> goes straight to the underlying MTD device.
>
> What kernel version? Can you give me a backtrace of the oops?

Kernel 2.2.12. The exact error message is as following:
bash# mount /dev/mtd0 /mnt
Unable to handle kernel NULL pointer dereference at virtual address 0000000c

current->tss.cr3 = 01676000, %cr3 = 01676000
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c014cd43>]
EFLAGS: 00010092
eax: c019549c   ebx: 00000000   ecx: 00000000   edx: 00000003
esi: 00000000   edi: 00000001   ebp: c15ba000   esp: c15bbcc8
ds: 0018   es: 0018   ss: 0018
Process mount (pid: 10, process nr: 7, stackpage=c15bb000)
Stack: 00000001 c0131c62 00000000 00000001 c0174880 c01b252c c0131f3f
00000001
       c01b252c 00000001 00000246 c15bbd28 c168f4d0 00000400 c014c190
00000000
       c012165a c01bb02c 00000001 c168f4d0 c168f4d0 c15bbe9c c15bbd28
c15bbd28
Call Trace: [<c0131c62>] [<c0174880>] [<c0131f3f>] [<c014c190>] [<c012165a>]
[<c01255ea>] [<c0121e2b>]
       [<c012208b>] [<c013ad74>] [<c0121e2b>] [<c012208b>] [<c013ad74>]
[<c0121e2b>] [<c012208b>] [<c012768c>]
       [<c01748a0>] [<c0111fa9>] [<c0131d0b>] [<c017489b>] [<c012126d>]
[<c01206e0>] [<c0120935>] [<c01079c8>]
Code: c7 46 0c 00 00 00 00 85 ff 75 44 ff 76 10 ff 74 24 1c 0f b7
Segmentation fault


Nick.



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-06-21  8:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <394F7351.BC878E0D@auriga.ru>
2000-06-20 14:16 ` garbage collect dwmw2
2000-06-21  8:06   ` Nick Ivanter [this message]
2000-06-23  9:39     ` David Woodhouse
2000-06-23  9:49       ` Nick Ivanter
     [not found] ` <394F88B3.1C046375@matrox.com>
2000-06-21  8:37   ` Nick Ivanter
2000-06-21  8:43     ` Nick Ivanter
     [not found] <Pine.LNX.3.96.1000628091427.16453B-100000@wakko.deltatee.com>
2000-06-28 16:05 ` David Woodhouse
2000-06-28 16:34   ` Jason Gunthorpe
2000-06-28 16:44     ` David Woodhouse
2000-06-28 18:20   ` Nicolas Pitre
2000-06-28 18:54     ` David Woodhouse
2000-06-28 19:33       ` Nicolas Pitre
2000-06-29 11:39         ` David Woodhouse
2000-07-03 15:12       ` Alan Cox
2000-07-03 16:09         ` David Woodhouse
2000-07-14 11:05         ` David Woodhouse

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=3950776D.30AC4B13@auriga.ru \
    --to=nick@auriga.ru \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=mtd@infradead.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