hi,
On 2019/02/26 14:00, Nils Frohberg wrote:
> On Mon, Feb 25, 2019 at 03:50:48PM -0300, Martin Pieuchot wrote:
>> On 25/02/19(Mon) 14:52, Nils Frohberg wrote:
[snip]
>>> I didn't get around to much testing/debugging lately, therefore I
>>> wanted to share the current state (diff below).
>>>
>>>
hi,
On 2019/02/28 06:53, Nils Frohberg wrote:
> On Tue, Feb 26, 2019 at 08:57:57PM +0200, Artturi Alm wrote:
>> On Tue, Feb 26, 2019 at 03:00:15PM +0100, Nils Frohberg wrote:
[snip]
>> Have you looked at what NetBSD has done with their axen(4)? there has
>> been 20commits in 2019 so far[0], while
Any there further interest in these patches? I was running these
since 61 days, doing lots of rsync and TimeMachine (netatalk)
backups. Didn't have any crashes or (noticeable) network dropouts.
$ uptime
11:05AM up 61 days, 16:54, 1 user, load averages: 0.35, 0.38, 0.38
$
On Thu, Feb 28, 2019 at
On Tue, Feb 26, 2019 at 08:57:57PM +0200, Artturi Alm wrote:
> On Tue, Feb 26, 2019 at 03:00:15PM +0100, Nils Frohberg wrote:
> > On Mon, Feb 25, 2019 at 03:50:48PM -0300, Martin Pieuchot wrote:
> > > On 25/02/19(Mon) 14:52, Nils Frohberg wrote:
> > > > Hi,
> > > >
> > > > as mentioned previously,
On Tue, Feb 26, 2019 at 03:00:15PM +0100, Nils Frohberg wrote:
> On Mon, Feb 25, 2019 at 03:50:48PM -0300, Martin Pieuchot wrote:
> > On 25/02/19(Mon) 14:52, Nils Frohberg wrote:
> > > Hi,
> > >
> > > as mentioned previously, I'm looking into axen(4). While searching
> > > for the cause of a panic
On Mon, Feb 25, 2019 at 03:50:48PM -0300, Martin Pieuchot wrote:
> On 25/02/19(Mon) 14:52, Nils Frohberg wrote:
> > Hi,
> >
> > as mentioned previously, I'm looking into axen(4). While searching
> > for the cause of a panic (fixed since, thanks mpi@) I started to
> > rewrite parts of the driver. R
On 25/02/19(Mon) 14:52, Nils Frohberg wrote:
> Hi,
>
> as mentioned previously, I'm looking into axen(4). While searching
> for the cause of a panic (fixed since, thanks mpi@) I started to
> rewrite parts of the driver. References were mainly the FreeBSD and
> Linux drivers.
Please try to isolate
Hi,
as mentioned previously, I'm looking into axen(4). While searching
for the cause of a panic (fixed since, thanks mpi@) I started to
rewrite parts of the driver. References were mainly the FreeBSD and
Linux drivers.
I didn't get around to much testing/debugging lately, therefore I
wanted to sh