netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Badalian Vyacheslav <slavon@bigtelecom.ru>
To: Jarek Poplawski <jarkao2@o2.pl>, netdev@vger.kernel.org
Subject: Re: Tc bug (kernel crash) more info
Date: Fri, 31 Aug 2007 12:25:22 +0400	[thread overview]
Message-ID: <46D7D072.5060508@bigtelecom.ru> (raw)
In-Reply-To: <20070831075909.GA1772@ff.dom.local>

i not have testing mashine.
we have 2 mashine and dynamic routing. if 1 mashine down - all traffic 
go to second mashine.
I can test is on this mashines but i need that testing mashine will 
reboot on kernel panic (sysctl message). No freezes =)

Ok. i try 2.6.23-rc4.

> On Fri, Aug 31, 2007 at 11:04:21AM +0400, Badalian Vyacheslav wrote:
>   
>> I try you patch. Also i try add more debug options to kernel. I catch 
>> (BUG: spinlock lockup on CPU#3, tc/6403, f742e200)
>> All info in file. Ready for next patch ;)
>>     
>
> I've to look at this, but actually my patch wrongly added this one
> warning. I hope you did this on a testing machine...
>
> Anyway there could be something new but I need some time. If possible,
> 2.6.23-rc4 should be the best thing for testing yet.
>
> Thanks,
> Jarek P.
>
>   


  reply	other threads:[~2007-08-31  8:25 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 [this message]
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
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=46D7D072.5060508@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).