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: Sun, 23 Mar 2003 17:51:10 +0000	[thread overview]
Message-ID: <marc-lartc-104844197131784@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104833907511635@msgid-missing>

On Sunday 23 March 2003 13:49, Julian Anastasov wrote:
> Hello,
>
> On Sat, 22 Mar 2003, Gordan Bobic wrote:
> > I seem to be having a problem with the newly applied patches, though.
> > After 6-8 hours, I get a kernel crash. Black screen od death, hex dumps,
> > Aiee, killing interrupt handler, trying to kill idle task, etc. This
> > happened twice, so it seems unlikely to be a coincidence, as the only
> > patches applied were the DS9, rtree, HTB3 and routes. It used to be
> > stable before. I am hoping that it is ingress related stuff that kills
> > it, so I have turned that off (everything to do with ingress). We'll see
> > if I get another crash now. If not, than it would appear that it is
> > ingress policing that kills it after a while.
> >
> > I will report back on this when I know more.
>
> 	ok, it is interesting where is the oops exactly (may be
> by avoiding modules and compiling qos in kernel). In any case,
> I created patch to upgrade to HTB 3.10

It would seem that the crash was DEFINITELY caused by ingress filtering. I 
have switched it off (while keeping all egress qdiscs and filters), and now 
the router has been up for 31 hours without a glitch. Oh, well. I will look 
into patching with the latest HTB, but since I don't use it, there seems to 
be little point...

Unfortunately, I cannot tell in which module the oops happens, because once 
the machine crashes, there are no logs and the start of the error scrolls off 
the screen. :-(

All I can tell for sure is that with ingress used it crashes, without it is 
fine.

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-23 17:51 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 ` Gordan Bobic [this message]
2003-03-24 22:32 ` [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic) Gordan Bobic

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-104844197131784@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.