From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Brian Vowell <brian.vowell@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Netdev <netdev@vger.kernel.org>,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10767] New: Seg Fault Instead of Swapping
Date: Mon, 26 May 2008 14:33:08 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805261426010.16829@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <cf4145200805230906k34a0452at773e840b791e6b0a@mail.gmail.com>
On Fri, 23 May 2008, Brian Vowell wrote:
> Here are some of the others that show in the logs:
>
> This one repeats four times, and then again multiple times every minute
> afterwards for about 30 minutes.
> May 18 19:31:00 ishtar kernel: pdflush: page allocation failure. order:3,
> mode:0x4020
I think that the problem here is that tg3 tries to allocate a large
contiguous memory block which isn't available.
> May 18 19:31:00 ishtar kernel: Pid: 15300, comm: pdflush Not tainted
> 2.6.25.4 #1
> May 18 19:31:00 ishtar kernel:
> May 18 19:31:00 ishtar kernel: Call Trace:
> May 18 19:31:00 ishtar kernel: <IRQ> [<ffffffff81075d35>]
> __alloc_pages+0x33f/0x35a
> May 18 19:31:00 ishtar kernel: [<ffffffff810934a4>] new_slab+0x3f/0x242
> May 18 19:31:00 ishtar kernel: [<ffffffff81093bba>]
> __slab_alloc+0x212/0x43b
> May 18 19:31:00 ishtar kernel: [<ffffffff8128654c>]
> __netdev_alloc_skb+0x29/0x43
> May 18 19:31:00 ishtar kernel: [<ffffffff8128654c>]
> __netdev_alloc_skb+0x29/0x43
> May 18 19:31:00 ishtar kernel: [<ffffffff81094bd6>]
> __kmalloc_node_track_caller+0x75/0xab
> May 18 19:31:00 ishtar kernel: [<ffffffff8128584a>] __alloc_skb+0x6a/0x133
> May 18 19:31:00 ishtar kernel: [<ffffffff8128654c>]
> __netdev_alloc_skb+0x29/0x43
> May 18 19:31:00 ishtar kernel: [<ffffffff8123a405>]
> tg3_alloc_rx_skb+0xc4/0x153
> May 18 19:31:00 ishtar kernel: [<ffffffff81241343>] tg3_poll+0x3be/0x7df
...but I'm probably not much of help with it.
--
i.
prev parent reply other threads:[~2008-05-26 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10767-10286@http.bugzilla.kernel.org/>
2008-05-21 17:57 ` [Bugme-new] [Bug 10767] New: Seg Fault Instead of Swapping Andrew Morton
[not found] ` <cf4145200805211140o3b2287dcsc57f8a78aa48a99d@mail.gmail.com>
2008-05-21 18:53 ` Andrew Morton
2008-05-21 20:18 ` Ilpo Järvinen
[not found] ` <cf4145200805211345y3b00d209o58e11a7b553cdfc6@mail.gmail.com>
2008-05-23 10:25 ` Ilpo Järvinen
[not found] ` <cf4145200805230906k34a0452at773e840b791e6b0a@mail.gmail.com>
[not found] ` <cf4145200805231024w2e735fb8ifecf7e2e1bab5957@mail.gmail.com>
2008-05-23 18:01 ` Ilpo Järvinen
[not found] ` <cf4145200805231126y401c2454w97e5305346aa8acd@mail.gmail.com>
2008-05-24 8:57 ` Ilpo Järvinen
[not found] ` <cf4145200805240706p2eb54e9ei51bc33f782ff5aef@mail.gmail.com>
2008-05-26 11:24 ` Ilpo Järvinen
2008-06-03 23:35 ` David Miller
2008-06-04 7:12 ` Ilpo Järvinen
2008-06-04 18:20 ` David Miller
2008-05-26 11:33 ` Ilpo Järvinen [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=Pine.LNX.4.64.0805261426010.16829@wrl-59.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=brian.vowell@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--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).