All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: for.poige+linux@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: re-formated /Re: Hi!Couldn't you take a look at kernel stack's trace? (ip_route_input+0x91a/0xcc9)/
Date: Thu, 12 Jun 2008 14:26:22 +0200	[thread overview]
Message-ID: <485115EE.1040204@trash.net> (raw)
In-Reply-To: <43d009740806120524g78d066d2x95640fc8e01be625@mail.gmail.com>

Igor Podlesny wrote:
> 2008/6/12 Patrick McHardy <kaber@trash.net>:
>>> Igor Podlesny wrote:
>>>>>  Pid: 8, comm: sirq-net-rx/0 Not tainted (2.6.25.4-rt4aa-gcc43 #1)
>                                             ^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> 	(2.6.25.4-rt4aa-gcc43)
> 	
> 	-RT is real-time: http://rt.wiki.kernel.org/index.php/Main_Page

Thanks, I missed that.

  reply	other threads:[~2008-06-12 12:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 14:36 re-formated /Re: Hi!Couldn't you take a look at kernel stack's trace? (ip_route_input+0x91a/0xcc9)/ Igor Podlesny
2008-06-12 12:07 ` Patrick McHardy
2008-06-12 12:24   ` Igor Podlesny
2008-06-12 12:26     ` Patrick McHardy [this message]
2008-06-12 19:36       ` Jarek Poplawski
2008-06-12 19:46         ` > with unpatched kernels, and if you tried other than 2.6.25 versions Igor M Podlesny
2008-06-12 20:15           ` Jarek Poplawski
2008-06-12 20:19             ` > Hm... hard to tell. This shouldn't happen and rebooting isn't a solution Igor M Podlesny
2008-06-12 20:49               ` Jarek Poplawski
2008-06-12 20:51                 ` > OK, a reboot after a bug can sometimes prevent further data corruption/loss Igor M Podlesny
2008-06-12 21:04                   ` Jarek Poplawski
2008-06-12 20:21             ` > try a more current kernel (e.g. 2.6.26-rc5) Igor M Podlesny
2008-06-12 20:39               ` Stephen Hemminger
2008-06-12 20:44                 ` > And kernel developer's can not afford debugging closed source drivers Igor M Podlesny
2008-06-12 20:23             ` > this message has strange "Subject" Igor M Podlesny

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=485115EE.1040204@trash.net \
    --to=kaber@trash.net \
    --cc=for.poige+linux@gmail.com \
    --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 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.