[PATCH] sparc64: Fix userspace FPU register corruptions.

2015-08-06 Thread David Miller
If we have a series of events from userpsace, with %fprs=FPRS_FEF, like follows: ETRAP ETRAP VIS_ENTRY(fprs=0x4) VIS_EXIT RTRAP (kernel FPU restore with fpu_saved=0x4) RTRAP We will not restore the user registers that were clobbered

(sparc[64]-specific pkgs) debian-ports: any BTS, PTS?

2015-08-06 Thread Bob Bib
Following the sparc removal[1], some sparc-specific source packages (e. g., silo & sparc-utils) have also been removed[2]. Obviously, they should be re-uploaded to debian-ports[3], to be built for sparc64. I wonder if the debian-ports have any package / bug tracking system, or is there any other

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Frans van Berckel
On Thu, 2015-08-06 at 16:57 +0200, Michael Biebl wrote: > Looks like this should be fixed in binutils for good instead of > having individual packages work around that. They are active changing the sources in git the past months. Searching for Sparc. Question, Is the bug stil there? https://sou

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Michael Biebl
Am 06.08.2015 um 16:13 schrieb d...@mattli.us: > Richard Mortimer writes: > >> So maybe the code is trying to use the wrong string as input to chdir >> and hence failing. > > Is udev using the gold linker during build? It is, indeed. We had a hack in debian/rules for a while, to use ld.bfd on

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread dmm
Richard Mortimer writes: > So maybe the code is trying to use the wrong string as input to chdir > and hence failing. Is udev using the gold linker during build? I've been looking into a bug where in certain circumstances, when linking with gold, string literal function arguments are corrupted.

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Richard Mortimer
On 06/08/2015 12:48, Artyom Tarasenko wrote: > Here is the correspondinf part of the gdb session with symbols from > systemd-dbg_224-1_sparc64.deb: > Many thanks. The log below pretty much does confirm that it is taking the suspected path through the code. Some steps are not visible to the debug

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Artyom Tarasenko
And here is an attempt to debug why parse_proc_cmdline fails: Breakpoint 3, main (argc=, argv=0x7fefc98) at ../src/udev/udevd.c:1662 1662r = parse_proc_cmdline(parse_proc_cmdline_item); (gdb) step parse_proc_cmdline (parse_item=0x1011180 ) at ../src/basic/util.c:4832 4832

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Artyom Tarasenko
Here is the correspondinf part of the gdb session with symbols from systemd-dbg_224-1_sparc64.deb: (gdb) run Starting program: /lib/systemd/systemd-udevd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/sparc64-linux-gnu/libthread_db.so.1". Breakpoint 3, main (

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Richard Mortimer
It looks like stdout and/or stderr output is mixed up with the strace output but it looks udevd is failing because the chdir to / fails. Notes inline below. (Caution I'm comparing against current systemd git HEAD and not any specific version) http://cgit.freedesktop.org/systemd/systemd/tree/src/u

Re: Bug#790560: udev fails to start on sparc boot, breaking boot

2015-08-06 Thread Artyom Tarasenko
That's what I see in the strace log: set_tid_address(0xf80100133790) = 9184 set_robust_list(0xf801001337a0, 24) = 0 rt_sigaction(SIGRTMIN, {0xf801006c6da0, [], SA_SIGINFO}, NULL, 0xf801006d2098, 8) = 0 rt_sigaction(SIGRT_1, {0xf801006c6c40, [], SA_RESTART|SA_SIGINFO}, NULL