From: Badalian Vyacheslav <slavon@bigtelecom.ru>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: netdev@vger.kernel.org
Subject: Re: Tc bug (kernel crash) more info
Date: Fri, 31 Aug 2007 14:48:31 +0400 [thread overview]
Message-ID: <46D7F1FF.1000101@bigtelecom.ru> (raw)
In-Reply-To: <20070831101733.GA3108@ff.dom.local>
> But sometime a new kernel can break binary compatibility with previous
> one (e.g. after data structures change) and e.g. iptables or iproute
> tools stop working or work in an unpredictable way. There were a few
> such changes before 2.6.20 - I don't track current changes too much.
> And I'm sure your system uses much more than iptables or TC, even
> without your knowledge.
>
I can rollback =) Backup system get all functions. I can risk for one
system of two for get and fix all bugs.
Dynamic routing work fine and automatic switch between systems = 1-4
seconds.
>> I send to you all info that catch NETCONSOLE. i don't cut any info...
>>
>
> So, it seems something was broken. But, I meant, there can be sometimes
> interesting things a few lines before or after the infos too.
>
I can only see that say netconsole. If i look to monitor i look last
lines. last line is "====...". Scrolling not work
netconsole run as module and start after system do full load. Then
netconsole is up - i run generator of tc scripts.
> BTW, -git versions are usually more risky than -rc. And, maybe, let
> this 2.6.18 better stay away from this testing...
>
I look changes between 2.6.23-rc4 and 2.6.23-rc4-git2 and think that
paches look good and no do any critical things =)
Now i do many script runs to simulate bug. if i get it on 2.6.23-rc4 - i
post it here. 2.6.23-rc4 not have htb_timer function.
Badalian Vyacheslav
next prev parent reply other threads:[~2007-08-31 10:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 9:34 Tc bug (kernel crash) more info Badalian Vyacheslav
2007-08-29 11:34 ` Jarek Poplawski
2007-08-29 12:14 ` Jarek Poplawski
2007-08-29 12:53 ` Badalian Vyacheslav
2007-08-29 13:30 ` Jarek Poplawski
2007-08-29 20:16 ` slavon
2007-08-30 6:31 ` Jarek Poplawski
2007-08-30 7:27 ` Jarek Poplawski
2007-08-30 9:09 ` Badalian Vyacheslav
2007-08-30 12:37 ` Jarek Poplawski
2007-08-30 13:43 ` Badalian Vyacheslav
2007-08-31 7:04 ` Badalian Vyacheslav
2007-08-31 7:59 ` Jarek Poplawski
2007-08-31 8:25 ` Badalian Vyacheslav
2007-08-31 8:49 ` Jarek Poplawski
2007-08-31 9:05 ` Jarek Poplawski
2007-08-31 9:16 ` Jarek Poplawski
2007-08-31 9:33 ` Badalian Vyacheslav
2007-08-31 10:17 ` Jarek Poplawski
2007-08-31 10:48 ` Badalian Vyacheslav [this message]
2007-08-31 12:59 ` Jarek Poplawski
2007-08-31 14:31 ` Badalian Vyacheslav
2007-08-31 14:51 ` Badalian Vyacheslav
[not found] ` <20070831215850.zf2xi256o00owk4s@mail.himki.net>
2007-09-01 10:36 ` slavon
2007-09-03 7:31 ` Jarek Poplawski
2007-09-03 8:05 ` Badalian Vyacheslav
2007-09-03 8:31 ` Badalian Vyacheslav
2007-09-03 9:12 ` Jarek Poplawski
2007-08-31 10:50 ` Badalian Vyacheslav
2007-08-31 10:59 ` Badalian Vyacheslav
2007-08-31 11:28 ` Jarek Poplawski
2007-08-31 12:14 ` Badalian Vyacheslav
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=46D7F1FF.1000101@bigtelecom.ru \
--to=slavon@bigtelecom.ru \
--cc=jarkao2@o2.pl \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).