[LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic)

[LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic)

[Gordan Bobic]

On Thursday 20 March 2003 23:36, Julian Anastasov wrote:
> Hello,
>
> On Thu, 20 Mar 2003, Gordan Bobic wrote:
> > Provided the DS9 patch works for me, is it possible to somehow prioritize
> > what is dropped first and what is dropped last? Something like attaching
> > a prio/cbq to the ingress qdisc? For example, I want SSH/POP3/IMAP4
> > traffic to be dropped last, and FTP/SMTP traffic to be dropped first. Can
> > ingress support in DS9 do this, or is it limited to indiscriminately
> > dropping traffic?
>
> 	Except if someone has another idea, may be only dropping.
> I'm not sure there is IMQ for 2.2 :)

It doesn't appear to be there with the patches I applied... :-(

> May be you can look at
> Edge31-ca-u32 from the iproute2 examples, there are some ideas
> about using policers.

I have tried the ingress policing when the new patches, but according to my 
mrtg graphs, it still doesn't seem to work, even in it's simplest form. I 
THINK I saw it work with FTP, though (connection throttled), so I am not 
sure. It could be that it works initially, then stops later. I will 
investigate further...

> As for DS9, it tries to provide the same
> interface to all qos objects as in 2.4, so it is possible to do
> the same things as in 2.4, of course, there is one problem, nobody
> wants to support new features in 2.2 :)

Yeah, I know. I will upgrade at some point. ;-)

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.

Regards.

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

Re: [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress

[Julian Anastasov]

	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

> Regards.
>
> Gordan

Regards

--
Julian Anastasov <ja@ssi.bg>

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

Re: [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic)

[Gordan Bobic]

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/

Re: [LARTC] 2.2.x crash after patching (Was: Prioritising Ingress Traffic)

[Gordan Bobic]

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/