On 06/05/2018 12:28 AM, Ian Campbell wrote:
> On Tue, 2018-06-05 at 02:14 +0100, Ben Hutchings wrote:
>
>> I don't think it's OK to cause a regression like this. Since this is
>> problem affects a specific known platform, the driver ought to
>> recognise it and disable itself automatically.
>
>
El 8 de junio de 2018 19:51:18 CEST, "Adam D. Barratt"
escribió:
>[Cc += debian-kernel]
>
>On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
>> On 15037 March 1977, Jonathan Wiltshire wrote:
>> > - May 26th (meaning freeze this coming weekend, which might be a
>> > big
>> > ask)
>>
>>
On Fri, Jun 08, 2018 at 06:51:18PM +0100, Adam Barratt wrote:
>[Cc += debian-kernel]
>
>On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
>> On 15037 March 1977, Jonathan Wiltshire wrote:
>> > - May 26th (meaning freeze this coming weekend, which might be a
>> > big
>> > ask)
>>
>> No.
>>
[Cc += debian-kernel]
On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
> On 15037 March 1977, Jonathan Wiltshire wrote:
> > - May 26th (meaning freeze this coming weekend, which might be a
> > big
> > ask)
>
> No.
>
> > - Jun 2nd (which may require an unusual SRM)
>
> Possible.
>
> >
Meanwhile my Debian Testing systems have (per default) upgraded to libbsd
0.9.1 (and kernel 4.16.0-2). Unfortunaetly, this does not fix the problem
(long ssdm start) under virtualization by kvm, although according to #898088
libvirt 0.9.0-1 should have alredy fixed this.
On productive bare metal I
5 matches
Mail list logo