From: Vladimir Serov <vserov@infratel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.arm.linux.org.uk
Subject: 2.4.2,3 nbd problem, works OK in 2.4.2-ac20,28
Date: Tue, 03 Apr 2001 16:16:04 +0400 [thread overview]
Message-ID: <3AC9BF03.AC0A6661@infratel.com> (raw)
Hello everybody,
I'm working on remote disks and swap for Strong ARM based board similar
to Brutus eval board (using usbnet Ethernet-over-USB driver). And i've
got problems with Network block device (nbd) i'm using to mount devices
exported from host computer. Every program trying access /dev/nbd0
after it was connected by nbd-client stops in D state.
My first thought was it's ARM specific, but later i found this problem
persists when using my host PC as client too. I've compiled nbd.o and
nbd-server (latest from cvs) with debug options turned on and use
"strace cat /dev/nd0" to see where it stuck. It looks like nbd actually
gets first page (4k) of data in several packets but user space doesn't
get this data and read system call does never return (this is the case
for 2.4.2-rmk1-np3 at least). I got this problem on 2.4.2-rmk1-np1,
2.4.2-rmk1-np3, 2.4.3 with Russell Kings patch for 2.4.3-pre7 kernels on
ARM and vanilla 2.4.2 and 2.4.3 kernels on ix86.
BUT !!!! 2.4.2-ac20,28 works fine on ix86 !!!! Possibly main branch
doesn't get updated.
Unfortunately the details of handling these requests aren't clear for me
and it's not simple to use Alan Cox patches on ARM cause there not
supported by Russell King and other people in ARM community (I mean no
patches again -acxx kernels) and i'm already overloaded by various beta
and alpha software.
Any help will be appreciated !!!
Thanks in advance.
Vladimir.
PS. sorry for bad english, it' my second language.
next reply other threads:[~2001-04-03 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 12:16 Vladimir Serov [this message]
2001-04-03 20:24 ` 2.4.2,3 nbd problem, works OK in 2.4.2-ac20,28 Russell King - ARM Linux
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=3AC9BF03.AC0A6661@infratel.com \
--to=vserov@infratel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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