From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: latest git crash (BUG/rt_fill_info)
Date: Fri, 5 Sep 2008 11:36:24 +0000 [thread overview]
Message-ID: <20080905113623.GB7320@ff.dom.local> (raw)
In-Reply-To: <200809041751.04163.denys@visp.net.lb>
On 04-09-2008 16:51, Denys Fedoryshchenko wrote:
> Single processor, working as NAT at office.
> I will try to reproduce the bug. Crash is happening on "light" traffic, after 10-20 minutes of usage.
>
> Sep 4 17:43:41 x.x.x.x [ 1084.917877] BUG: unable to handle kernel
> Sep 4 17:43:41 x.x.x.x paging request
> Sep 4 17:43:41 x.x.x.x at 84e8dc55
> Sep 4 17:43:41 x.x.x.x [ 1084.917943] IP:
> Sep 4 17:43:41 x.x.x.x [<c02826be>] rt_fill_info+0x329/0x33f
I guess it would be helpful to put vmlinux from this kernel build
under some link (or send some gdb listing of this address).
Jarek P.
prev parent reply other threads:[~2008-09-05 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 14:51 latest git crash (BUG/rt_fill_info) Denys Fedoryshchenko
2008-09-05 11:36 ` Jarek Poplawski [this message]
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=20080905113623.GB7320@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=denys@visp.net.lb \
--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