On Mon, 2015-07-13 at 04:31 +1000, Peter Jeremy wrote:
> On 2015-Jul-12 09:41:43 -0600, Ian Lepore wrote:
> >And let's all just hope that a week or two of testing is enough when
> >jumping a major piece of software forward several years in its
> >independent evolution.
>
> Whilst I support John's
On 2015-Jul-13 04:31:40 +1000, Peter Jeremy wrote:
>>The import of 4.2.8p2 several months ago resulted in complete failure of
>>timekeeping on all my arm systems. Just last week I tracked it down to
>>a kernel bug (which I haven't committed the fix for yet). While the bug
>>has been in the kerne
On 2015-Jul-12 09:41:43 -0600, Ian Lepore wrote:
>And let's all just hope that a week or two of testing is enough when
>jumping a major piece of software forward several years in its
>independent evolution.
Whilst I support John's desire for NTP to be updated, I also do not
think this is the appr
And let's all just hope that a week or two of testing is enough when
jumping a major piece of software forward several years in its
independent evolution.
The import of 4.2.8p2 several months ago resulted in complete failure of
timekeeping on all my arm systems. Just last week I tracked it down t
Bezüglich Edward Tomasz Napierała's Nachricht vom 12.07.2015 11:41
(localtime):
> On 0711T1956, Harald Schmalzbauer wrote:
>> Hello,
>>
>> r284665 causes ahci(4) to fail with timeouts when using MSI (the default).
> What's the hardware?
Thanks for your attention,
it's Intel Cougar Point (C204,
Wow! Thanks for your time and quick response.
I'm looking forward to seeing it MFCed. :-)
On Sun, 12 Jul 2015 08:56:26 +
Xin LI wrote:
> I've spent some time on the MFC, the testing would still take some time
> (likely a day or two) and once that's finished I'll ask re@ for approval.
> On Sa
On 0711T1956, Harald Schmalzbauer wrote:
> Hello,
>
> r284665 causes ahci(4) to fail with timeouts when using MSI (the default).
What's the hardware?
> 'hint.ahci.0.msi=0' is one way to make ahci(4) working with r284665, but
> obviously not the desired solution, it just disables usage of an MSI
I've spent some time on the MFC, the testing would still take some time
(likely a day or two) and once that's finished I'll ask re@ for approval.
On Sat, Jul 11, 2015 at 11:44 PM Tomoaki AOKI
wrote:
> As I already mentioned in another post, head has 4.2.8 p3 in-tree.
>
> So the answer should be M
On Jul 11 23:22, Chris Nehren wrote:
On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:
It's me again with my annual NTP whinge.
The answer to the perennial "will release $foo ship with old / insecure
/ otherwise deficient $bar?" is still "install $bar from ports".
I completely ag
