All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordan Bobic <lartc@bobich.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic)
Date: Mon, 24 Mar 2003 22:32:35 +0000	[thread overview]
Message-ID: <marc-lartc-104854523113089@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104833907511635@msgid-missing>

Hi.

I have just had another very similar crash. It would appear that it is not 
related specifically to ingress policing. It appears to also happen using 
just egress cbq/sfq. However, the uptime between crashes has increased from 
around 6 hours to over 24 hours with ingress filtering switched off, with 
similar (and probably heavier) usage.

Unfortunately, I can still find nothing useful in the logs, and there was 
nothing useful on the screen either (just a hex dump).

I have had this problem (or a very similar one with the same symptoms) before 
with QoS on earlier, unpatched v2.2.x kernels (circa 2.2.14 era). Has anybody 
else experienced/reported anything similar?

I guess I'll just have to upgrade to v2.4...

Regards.

Gordan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-03-24 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-22 13:16 [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic) Gordan Bobic
2003-03-23 13:49 ` [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Julian Anastasov
2003-03-23 17:51 ` [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic) Gordan Bobic
2003-03-24 22:32 ` Gordan Bobic [this message]

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-104854523113089@msgid-missing \
    --to=lartc@bobich.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.