--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nfs-kernel-server: NFS server doesn't respond to client after booting firefox on the client machine
- From: Borna Novak <bbozo@student.math.hr>
- Date: Wed, 12 Jan 2005 15:57:43 +0100
- Message-id: <E1CojwN-0002Ii-00@borna0>
Package: nfs-kernel-server
Version: 1:1.0.6-3.1
Severity: normal
I was using the latest sarge nfs-kernel-server and was then forced to
change kernels. I downloaded debian kernel-source-2.6.8 and took the
config file from kernel-image-2.6.8-1-k7 and then changes k7 to k6 (in
the .config), compiled it (using make-kpkg) and compiled (manually,
without make-kpkg) atmel usb drivers at76c503a from the latest cvs (as
advised on the website).
Everything works, but when I try to run mozilla-firefox or xmms on the machine that mounts /home via nfs, the nfs server stops responding to client requests. (jnettop on server reports a steady RX of 1-2kb/s on 800/udp, but nothing out, syslog reports nothing)
I tried the sid nfs-kernel-server package but with no luck.
I tried upgradeing nfs-common (nfs-common reported "mount version older
than kernel" during bootup but no newer mount version is availible).
The client machine runs untainted kernel-image-2.6.8-1-k7 and the latest mount and nfs-common from sarge.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.6.8-borna0
Locale: LANG=hr_HR, LC_CTYPE=hr_HR (charmap=ISO-8859-2)
Versions of packages nfs-kernel-server depends on:
ii debconf 1.4.30.10 Debian configuration management sy
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libwrap0 7.6.dbs-6 Wietse Venema's TCP wrappers libra
ii nfs-common 1:1.0.6-3.1 NFS support files common to client
ii sysvinit 2.86-5 System-V like init
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 290042-done@bugs.debian.org
- Subject: Re: Bug#290042: nfs-kernel-server: NFS server doesn't respond to client after booting firefox on the client machine
- From: Jurij Smakov <jurij@wooyd.org>
- Date: Thu, 27 Apr 2006 00:19:50 -0700 (PDT)
- Message-id: <Pine.LNX.4.63.0604270017230.2774@bobcat>
- Reply-to: jurij@wooyd.org
- In-reply-to: <ca9ca1120604270015r334d030djfb56d1b0ea485a45@mail.gmail.com>
- References: <Pine.LNX.4.63.0604192248300.17373@bobcat> <ca9ca1120604200245w26fae884x1957062fe2101f93@mail.gmail.com> <Pine.LNX.4.63.0604270001340.2712@bobcat> <ca9ca1120604270015r334d030djfb56d1b0ea485a45@mail.gmail.com>
On Thu, 27 Apr 2006, Borna Novak wrote:
It's probably water under the bridge by now :-) I would close the bug, but
the domain on the e-mail address seems wrong:)
.d.o is a pretty common abbreviation for .debian.org :-). Anyway, I'm
closing the bug by this mail, thanks for a quick response!
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--- End Message ---