Package: src:linux
Version: 5.14.16-1
Severity: normal
X-Debbugs-Cc: rincebr...@gmail.com
Dear Maintainer,
Trying to boot a recent sparc64 disc on this T5140, it dies on boot with
something like:
[ 52.521656] niu: niu.c:v1.1 (Apr 22, 2010)
[ 52.529379] niu: niu0: Found PHY 002063b0 type MII
Trent W. Buck wrote:
> 3. A single mount(2) call also works!
>
> It is quite annoying that we need *anything* special in userland, because
> a nfsvers=4.2,sec=sys mount requires only 2049/tcp (no other ports/services),
> and
> the actual filesystem is in-kernel, so
> really all that should be n
Short version:
1. nfsmount(8klibc) is still explicitly broken for NFSv4.
2. mount.nfs(8nfs-utils) works in the ramdisk.
3. A single mount(2) call also works!
Boring detailed version follows.
John Goerzen wrote:
> nfsmount is incapable of mounting NFSv4 filesystems. It seems to have
> sup
Package: src:linux
Version: 5.14.16-1
Followup-For: Bug #998799
Just tested the new kernel image on my AMD Ryzen 5 2400G and I see the
same problem. Initially I thought the system was dead due to the long
delays introduced in the boot process.
Here are the relevant lines from the kernel log:
dz
4 matches
Mail list logo
