From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: RE:RE:[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
Date: Thu, 03 Jul 2003 11:02:49 +0000 [thread overview]
Message-ID: <marc-lartc-105723061108157@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105722941707305@msgid-missing>
Ok, try please 2.4.21. Also can you trigger the bug
often or only sometimes ? Does it depend on traffic ?
I'm looking how to reproduce it here ..
On Thu, 3 Jul 2003 lartc@go.ro wrote:
> OK No problem!
> I'm useing Slack 9.0/2.4.20( AMD K6 2-333Mhz with RAM 128MB) with HTB from
> kernel...and U32 filters!
> /* How can I tweak bash or something ...to get high histoy on Shift+PageUP
> and a higher bashhistory, too */
> The dmesg paste:
> KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
> KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
> KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
> KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
> KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
> KERNEL: assertion (cl && cl->un.leaf.q->q.qlen) failed at sch_htb.c(959)
> eth0: Promiscuous mode enabled.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-03 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 10:44 RE:RE:[LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen) lartc
2003-07-03 11:02 ` Martin Devera [this message]
2003-07-03 11:14 ` lartc
2003-07-03 12:48 ` David Watson
2003-07-03 13:35 ` lartc
-- strict thread matches above, loose matches on Subject: below --
2003-07-03 10:25 lartc
2003-07-03 10:30 ` Martin Devera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105723061108157@msgid-missing \
--to=devik@cdi.cz \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox