| 1 |
On 04/01/20 11:09, Rolf Eike Beer wrote: |
| 2 |
> Am Freitag, 3. Januar 2020, 11:00:14 CET schrieb Rolf Eike Beer: |
| 3 |
>> Am Freitag, 3. Januar 2020, 03:40:35 CET schrieb Aaron Bauman: |
| 4 |
>>> On January 2, 2020 6:35:08 PM EST, Rolf Eike Beer <eike@×××××××.de> wrote: |
| 5 |
>>>> Am Freitag, 3. Januar 2020, 00:25:06 CET schrieb Mike Pagano: |
| 6 |
>>>>> hppa is making us keep old kernels around [1]. Should the kernel team |
| 7 |
>>>>> be |
| 8 |
>>>>> doing more to get your attention then CC'ing hppa on all of the kernel |
| 9 |
>>>>> STABLEREQ bugs [2]? |
| 10 |
>>>> I only run vanilla-sources since there are still lot of cache |
| 11 |
>>>> corruption |
| 12 |
>>>> problems in hppa kernels, or whatever makes them flaky. |
| 13 |
>>>> |
| 14 |
>>>> Linux pioneer 5.4.6-parisc64 #1 SMP Fri Dec 27 10:23:09 CET 2019 parisc64 |
| 15 |
>>>> PA8800 (Mako) 9000/785/C8000 GNU/Linux |
| 16 |
>>>> Linux voyager 5.4.6-parisc #1 Fri Dec 27 15:46:43 CET 2019 parisc PA8600 |
| 17 |
>>>> (PCX-W+) 9000/785/C3600 GNU/Linux |
| 18 |
>>>> |
| 19 |
>>>> So _I_ personally would say just drop old kernels, but that is in no |
| 20 |
>>>> way |
| 21 |
>>>> authorative. |
| 22 |
>>> Ugh. gentoo-sources is just a patch (trivial) on top of vanilla-kernel |
| 23 |
>>> sources of each stable and LTS version. |
| 24 |
>> If it's just that I could test them, but this still be no LTS version that I |
| 25 |
>> would look at. |
| 26 |
> So, do you want me to stable a random gentoo-sources (usually the most recent |
| 27 |
> one) every few weeks when I just happen to upgrade my machine? |
| 28 |
> |
| 29 |
> Eike |
| 30 |
I don't think that works very well with kernel/security-team stabilisation |
| 31 |
policies, sadly. |
| 32 |
|
| 33 |
Is there any possibility you would be able to do a stabilisation run, and |
| 34 |
do a reboot cycle on one LTS branch (of choice, eg. most recent) and then |
| 35 |
revert to your preferred kernel afterwards? |
| 36 |
|
| 37 |
I appreciate this is a rather onerous process on older hardware, but just |
| 38 |
trying to think of some form of semi-compromise that prevents potential |
| 39 |
de-keywording, without also suggesting that something that genuinely has |
| 40 |
issues is either (1) working or (2) supported, if so. |
| 41 |
|
| 42 |
I believe Whissi is leading kernel stabilisation requests, on behalf of |
| 43 |
security- and kernel- teams, so maybe a chat with him may be fruitful. |
| 44 |
Cheers, |
| 45 |
veremitz/Michael. |
Archives