1 |
On 02/17/2016 05:46 PM, Mike Frysinger wrote: |
2 |
> On 17 Feb 2016 17:11, Alex McWhirter wrote: |
3 |
>> On 02/14/2016 09:13 PM, Mike Frysinger wrote: |
4 |
>>> On 14 Feb 2016 18:44, Alex McWhirter wrote: |
5 |
>>>> Using vanilla kernels, 3.18.26 is the last kernel that seems to work. |
6 |
>>>> 4.1.17 introduces the issue. Is this something worth bringing up on the |
7 |
>>>> sparc kernel mailing list? I'm currently scouring through a 4.1.17 / |
8 |
>>>> 3.18.26 diff which is so large it's hard to get anywhere. |
9 |
>>> erm, there are kernel versions inbetween those. can you not try 3.19, |
10 |
>>> 4.0, or 4.1 from kernel.org ? |
11 |
>> Well after a few days of building kernels (each one takes about 5 hours |
12 |
>> on this box :/)... |
13 |
>> |
14 |
>> 3.18.26 - Works |
15 |
>> 3.19.0 - Dead |
16 |
>> |
17 |
>> So it looks like 3.19.0 added the issue. |
18 |
> feel like bisecting it further ? you can clone: |
19 |
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ |
20 |
> |
21 |
> and then run: |
22 |
> $ git bisect start v3.19 v3.18 |
23 |
> |
24 |
> and then try building/booting each combo it comes up with. if it fails, |
25 |
> run `git bisect bad`. if it passes, run `git bisect good`. if it does |
26 |
> not compile (sometimes that happens), you can use `git bisect skip`. |
27 |
> -mike |
28 |
|
29 |
Well one way or another someone has to do it right? |
30 |
|
31 |
Time to get back to the lonely world of constantly compiling kernels... |