From: Igor M Podlesny <for.poige+linux@gmail.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: > with unpatched kernels, and if you tried other than 2.6.25 versions
Date: Fri, 13 Jun 2008 03:46:36 +0800 [thread overview]
Message-ID: <48517D1C.7010308@gmail.com> (raw)
In-Reply-To: <48517ACD.4020209@gmail.com>
On 2008-06-13 03:36, Jarek Poplawski wrote:
> Patrick McHardy wrote, On 06/12/2008 02:26 PM:
[...]
>
> Igor, probably for this list it's more interesting if it's reproducible
> with unpatched kernels, and if you tried other than 2.6.25 versions
> for this?
>
> Thanks,
> Jarek P.
Recently I got another one (several times, actually):
[105373.451522] swapper: page allocation failure. order:2, mode:0x4020
[105373.451527] Pid: 0, comm: swapper Tainted: P 2.6.25.6aa-gcc43 #1
[105373.451540] [<c0157670>] __alloc_pages+0x2af/0x2c7
[105373.451550] [<c015770f>] __get_free_pages+0x3c/0x4d
[105373.451553] [<c02ec2e1>] __alloc_skb+0x49/0xf6
[105373.451558] [<f8b65b9d>] nv_alloc_rx_optimized+0x45/0x15d [forcedeth]
[105373.451567] [<f8b6a768>] nv_napi_poll+0x50f/0x5e7 [forcedeth]
[105373.451577] [<c02ef173>] net_rx_action+0x65/0x158
[105373.451582] [<c012fa8a>] __do_softirq+0x5a/0xa8
[105373.451588] [<c012fb0a>] do_softirq+0x32/0x36
[105373.451591] [<c012fc5f>] irq_exit+0x35/0x76
[105373.451594] [<c01157c7>] do_IRQ+0x54/0x65
[105373.451599] [<c0113c0f>] common_interrupt+0x23/0x28
[105373.451607] [<c011238c>] default_idle+0x36/0x5a
[105373.451610] [<c0112356>] default_idle+0x0/0x5a
[105373.451613] [<c0112326>] cpu_idle+0x8c/0xbc
[105373.451620] =======================
$ uname -sr
Linux 2.6.25.6aa-gcc43
BTW, it's unclear, would it be better to have rebooted the comp. immediately after
getting those messages?
--
next prev parent reply other threads:[~2008-06-12 19:46 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
2008-06-12 19:36 ` Jarek Poplawski
2008-06-12 19:46 ` Igor M Podlesny [this message]
2008-06-12 20:15 ` > with unpatched kernels, and if you tried other than 2.6.25 versions 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=48517D1C.7010308@gmail.com \
--to=for.poige+linux@gmail.com \
--cc=jarkao2@gmail.com \
--cc=kaber@trash.net \
--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.