re: kern/51057: hme(4) device driver bug when tcp4csum and udp4csum are enabled

To: matthew green <mrg%eterna.com.au@localhost>
Subject: re: kern/51057: hme(4) device driver bug when tcp4csum and udp4csum are enabled
From: Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>
Date: Sun, 10 Apr 2016 23:06:38 +0200

On Mon, 11 Apr 2016 06:09:29 +1000, matthew green wrote:
> i have this memory of people saying quad hme(4) @ sbus was a problem
> a *long* time ago.

I ran NetBSD on an SS20 with a quad hme as a router 24/7 for a few 
years. It was replaced because the SM71 cpus died, not because of the 
hme.

FWIW,
hauke

-- 
Hauke Fath                        <hauke%Espresso.Rhein-Neckar.DE@localhost>
Ernst-Ludwig-Straße 15
64625 Bensheim
Germany

References:
- re: kern/51057: hme(4) device driver bug when tcp4csum and udp4csum are enabled
  - From: matthew green

Prev by Date: Re: bin/50705 (DHCP client daemon broken in NetBSD 7.0 INSTALL image)
Next by Date: re: kern/51057: hme(4) device driver bug when tcp4csum and udp4csum are enabled
Previous by Thread: re: kern/51057: hme(4) device driver bug when tcp4csum and udp4csum are enabled
Next by Thread: re: kern/51057: hme(4) device driver bug when tcp4csum and udp4csum are enabled
Indexes:

Home | Main Index | Thread Index | Old Index