[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <18788C50-F29B-4BD7-89F6-B056FF490214@goldelico.com>
Date: Thu, 7 Nov 2019 17:21:13 +0100
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Vincenzo Frascino <vincenzo.frascino@....com>
Cc: Ralf Baechle <ralf@...ux-mips.org>,
Paul Burton <paul.burton@...s.com>,
MIPS Creator CI20 Development
<mips-creator-ci20-dev@...glegroups.com>,
Discussions about the Letux Kernel
<letux-kernel@...nphoenux.org>, linux-mips@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: MIPS: bug: gettimeofday syscall broken on CI20 board?
Hi,
I am trying to run v5.4-rc6 on the CI20 board (jz4780) and it
is almost ok. Except one strange thing.
If I install a v4.19.81 kernel I can initialize the
ethernet interface and dhclient works.
If I install a v5.4-rc6 kernel on exactly the same
rootfs dhclient fails with
root@...ux:~# dhclient
../../../../lib/isc/unix/time.c:200: Operation not permitted
root@...ux:~#
I have done some strace and the first significant difference
is that with v5.4-rc6 there is no gettimeofday syscall.
Another symptom pointing in the same direction is that
after manually assigning an IP address I can run ping
but get strange time values.
So it may be that
24640f233b46 mips: Add support for generic vDSO
did break gettimeofday when used with latest Debian Stretch
libraries. I tried to git revert but there are conflicts.
Just a side-note: both kernels work with Debian Jessie,
which likely has an older gettimeofday wrapper that
is not influenced by some subtle change.
BR and thanks,
Nikolaus Schaller
Powered by blists - more mailing lists