1 |
On 13 Feb 2016 16:26, Alex McWhirter wrote: |
2 |
> On 02/13/2016 12:32 PM, Alex McWhirter wrote: |
3 |
> > On 02/13/2016 06:25 AM, Mike Frysinger wrote: |
4 |
> >> On 13 Feb 2016 04:26, Alex McWhirter wrote: |
5 |
> >>> Well, time for more fun |
6 |
> >>> |
7 |
> >>> Copying over the 3.4.14 kernel from the install cd will make rsync work. |
8 |
> >>> |
9 |
> >>> Kernel 4.1.12 rsync is dead |
10 |
> >>> Kernel 4.1.15 rsync is dead |
11 |
> >>> |
12 |
> >>> Since all sparc profiles use a 64bit kernel i would be heavily |
13 |
> >>> interested in what kernel / options you are running. |
14 |
> >> Linux bender 3.17.2 #2 SMP Tue Nov 11 18:56:20 UTC 2014 sparc64 sun4v UltraSparc T1 (Niagara) GNU/Linux |
15 |
> >> |
16 |
> >> [ 0.000000] Linux version 3.17.2 (root@bender) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.5, pie-0.5.5) ) #2 SMP Tue Nov 11 18:56:20 UTC 2014 |
17 |
> >> |
18 |
> >> config is attached |
19 |
> >> |
20 |
> >>> Using the kernel config from the CD on a newer kernel still results in a |
21 |
> >>> broken rsync. So the kernel is either broken somehow or there's an |
22 |
> >>> option somewhere that genkernel, the cd config, and myself are missing. |
23 |
> >> or the toolchain is unhappy |
24 |
> > |
25 |
> > It's fairly likely that you will break rsync as well if you upgrade to a |
26 |
> > 4.X kernel as i have experienced this with an official install on |
27 |
> > another box. I'm working on building a 3.14 kernel with a newer |
28 |
> > toolchain to see what happens. 4.4.1 still has this issue, i may try |
29 |
> > vanilla sources as well after 3.14. |
30 |
> > |
31 |
> > I suppose its also likely that this could be a bug in rsync as well that |
32 |
> > may have been relying on a bug in older kernels which was later fixed. |
33 |
> > But this is all speculation at this point. |
34 |
> |
35 |
> 3.14.58 works fine when built with the latest toolchain. I had to use |
36 |
> the CD config, as genkernel doesn't have correct sparc settings and i |
37 |
> didn't feel like manually configuring it just to see if rsync worked |
38 |
> afterwards. The fun part will be finding which exact kernel introduced |
39 |
> the breakage, or perhaps it could be an rsync bug as the rest of the |
40 |
> system works fine on newer kernels. Even if it is an issue with rsync, |
41 |
> finding the kernel the breaks this functionality might help narrow down |
42 |
> the issue. |
43 |
|
44 |
agreed -- if we can narrow down the kernel range, that should help with |
45 |
triaging |
46 |
-mike |