From: Frank Oltmanns <frank.oltmanns.ml@gmx.de>
To: linux-mtd@lists.infradead.org
Subject: Root-FS on DOC2000 (was Re: Compiling Grub for DOC2000)
Date: Wed, 31 Jul 2002 13:22:29 +0200 (MEST) [thread overview]
Message-ID: <712.1028114549@www55.gmx.net> (raw)
In-Reply-To: 14743.1028068151@redhat.com
>
> frank.oltmanns.ml@gmx.de said:
> > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> > ######################################
> > # I get this far when I use DoC as the root-fs #
> > ######################################
> > Looking up port of RPC 100003/2 on 192.168.1.99
> > Looking up port of RPC 100005/1 on 192.168.1.99
>
> Remove the bogus invalidate_device() from the mtdblock_release() function
> in drivers/mtd/mtdblock.c.
I did, but nothing happened.
Here is what I get, when using DoC as root-fs (debug-level 3) after the
"NET4: Unix domain sockets 1.0/SMP for Linux NET4.0" -line:
NFTL_open
NFTL_open
NFTL_request
NFTL Read request, from sector 0x0002 for 0x0002 sectors
Waiting for mutex
Got mutex
NFTL read request of 0x2 sectors @ 3 (req->nr_sectors == 2)
NFTL read request completed OK
end_request(1)
NFTL_request
NFTL Read request, from sector 0x0004 for 0x0002 sectors
Waiting for mutex
Got mutex
NFTL read request of 0x2 sectors @ 5 (req->nr_sectors == 2)
NFTL read request completed OK
end_request(1)
NFTL_request
NFTL Read request, from sector 0x000a for 0x0002 sectors
Waiting for mutex
Got mutex
NFTL read request of 0x2 sectors @ b (req->nr_sectors == 2)
NFTL read request completed OK
end_request(1)
NFTL_request
NFTL Write request, from sector 0x0002 for 0x0002 sectors
Waiting for mutex
Got mutex
NFTL read request of 0x2 sectors @ 3 (req->nr_sectors == 2)
Status of block 3 in EUN 1023 is 55
Status of block 3 in EUN 36 is 55
Status of block 3 in EUN 133 is 55
Status of block 3 in EUN 134 is 55
Status of block 3 in EUN 135 is 55
Status of block 3 in EUN 140 is 55
Status of block 3 in EUN 774 is 55
Status of block 3 in EUN 776 is 55
_DoC_WaitReady called for out-of-line wait
_DoC_WaitReady called for out-of-line wait
_DoC_WaitReady called for out-of-line wait
_DoC_WaitReady called for out-of-line wait
Status of block 4 in EUN 1023 is 55
Status of block 4 in EUN 36 is 55
Status of block 4 in EUN 133 is 55
Status of block 4 in EUN 134 is 55
Status of block 4 in EUN 135 is 55
Status of block 4 in EUN 140 is 55
Status of block 4 in EUN 774 is 55
Status of block 4 in EUN 776 is 55
Status of block 4 in EUN 1022 is ff
_DoC_WaitReady called for out-of-line wait
_DoC_WaitReady called for out-of-line wait
NFTL write request completed OK
end_request(1)
NFTL_release
1) I don't know what all of this means. Perhaps someone
can explain that or tell me what is wrong.
2) Why are there two NFTL_open-calls and only one
NFTL_release?
Thanks in advance
Frank
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
next prev parent reply other threads:[~2002-07-31 11:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 13:21 Compiling Grub for DOC2000 Frank Oltmanns
2002-07-26 13:43 ` Mark Meade
2002-07-26 15:18 ` David Woodhouse
2002-07-26 16:35 ` Ilguiz Latypov
2002-07-29 15:28 ` Frank Oltmanns
2002-07-29 16:24 ` Ilguiz Latypov
2002-07-30 13:45 ` Frank Oltmanns
2002-07-30 22:29 ` David Woodhouse
2002-07-31 11:22 ` Frank Oltmanns [this message]
2002-07-31 11:48 ` Root-FS on DOC2000 (was Re: Compiling Grub for DOC2000) David Woodhouse
2002-07-31 14:00 ` Frank Oltmanns
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=712.1028114549@www55.gmx.net \
--to=frank.oltmanns.ml@gmx.de \
--cc=linux-mtd@lists.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 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.