On Fri, Nov 20, 2020 at 02:01:55PM +0100, Claudio Jeker wrote:
> On Fri, Nov 20, 2020 at 11:32:18AM +0100, Otto Moerbeek wrote:
> > On Fri, Nov 20, 2020 at 11:09:25AM +0100, Mark Kettenis wrote:
> >
> > > It's a relatively new driver. It uses MSI which pretty much rules out
> > > an issue with shared interrupts. So I suspect this is an issue with
> > > the rge(4) driver. In the past we have fun with packet counter
> > > overflow interrupts. Is the storm present immediately after you bring
> > > up the interface? Or even before?
> >
> > No storm if not configured and no cable plugged in.
> > No storm if not configured and cable plugged in
> > No storm if configured and no cable
> >
> > Storm start when I plug the cable in.
>
> Sounds like an unexpected interrupt source that should probably be masked.
>
> I would look at rge_intr() and what status you get and compare it to the
> RGE_ISR defines. This may help to figure out what is going on.
>
> --
> :wq Claudio
The value of status after the RGE_READ_4 call is 0x10 all the time:
RGE_ISR_RX_DESC_UNAVAIL
-Otto
