On Thu, Jun 01, 2017 at 10:30 +0200, Mike Belopuhov wrote:
> On Mon, May 29, 2017 at 14:16 +0200, Mike Belopuhov wrote:
> > Thanks for taking your time to test, but unfortunately I have to
> > withdraw both diffs. I've realised that there's a ton of drivers
> > calling ifq_deq_begin manually from
On Mon, May 29, 2017 at 14:16 +0200, Mike Belopuhov wrote:
> Thanks for taking your time to test, but unfortunately I have to
> withdraw both diffs. I've realised that there's a ton of drivers
> calling ifq_deq_begin manually from their start routines and
> there's no simple solution for that
On Mon, May 29, 2017 at 06:57 +0200, Sebastien Marie wrote:
> On Sun, May 28, 2017 at 10:45:34PM +0200, Mike Belopuhov wrote:
> > >
> > > mikeb@, I don't reproduce if I backout the local diff.
> > >
> > > it seems bce(4) doesn't like it.
> >
> > Indeed, a lot of things won't like this since
On Sun, May 28, 2017 at 10:45:34PM +0200, Mike Belopuhov wrote:
> >
> > mikeb@, I don't reproduce if I backout the local diff.
> >
> > it seems bce(4) doesn't like it.
>
> Indeed, a lot of things won't like this since xxx_start may be called
> directly by the driver. To handle this situation
On Sat, May 27, 2017 at 20:06 +0200, Sebastien Marie wrote:
> On Sat, May 27, 2017 at 07:28:26AM +0200, Sebastien Marie wrote:
> > Hi,
> >
> > I am experiencing often the following panic:
> >
> > panic: kernel diagnostic assertion "ifq_is_serialized(ifq)" failed:
> > ../sys/net/ifq.c, line 394
On Sat, May 27, 2017 at 07:28:26AM +0200, Sebastien Marie wrote:
> Hi,
>
> I am experiencing often the following panic:
>
> panic: kernel diagnostic assertion "ifq_is_serialized(ifq)" failed:
> ../sys/net/ifq.c, line 394
>
> while running with GENERIC.MP patched with mikeb@ diff:
>
>
Hi,
I am experiencing often the following panic:
panic: kernel diagnostic assertion "ifq_is_serialized(ifq)" failed:
../sys/net/ifq.c, line 394
while running with GENERIC.MP patched with mikeb@ diff:
if_start(struct ifnet *ifp)
{
KASSERT(ifp->if_qstart == if_qstart_compat);
-
