From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 6
Date: Fri, 7 Aug 2009 15:15:45 +0200 [thread overview]
Message-ID: <200908071515.45169.bzolnier@gmail.com> (raw)
In-Reply-To: <200908062250.51498.bzolnier@gmail.com>
On Thursday 06 August 2009 22:50:50 Bartlomiej Zolnierkiewicz wrote:
> On Thursday 06 August 2009 11:22:09 Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20090805:
>
> At the moment -next is completely unusable for anything other than
> detecting merge conflicts.. Running -next was never a completely
> smooth experience but for a past year it was more-or-less doable.
> However the last two months have been an absolute horror and I've
> been hitting issues way faster than I was able to trace/report
> them properly..
>
> Right now I still have following *outstanding* issues (on just *one*
> machine/distribution):
>
> - Random (after some long hours) order:6 mode:0x8020 page allocation
> failure (when ipw2200 driver reloads firmware on firmware error).
>
> [ I had first thought that it was caused by SLQB (which got enabled
> as default somewhere along the way) but it also happens with SLUB
> and I have good reasons to believe that is caused by heavy mm
> changes first seen in next-20090618 (I've been testing next-20090617
> for many days and it never happened there), the last confirmed
> release with the problem is next-20090728. ]
If anyone is interested in the full log of the problem:
ipw2200: Firmware error detected. Restarting.
ipw2200/0: page allocation failure. order:6, mode:0x8020
Pid: 1004, comm: ipw2200/0 Not tainted 2.6.31-rc4-next-20090728-04869-gdae50fe-dirty #51
Call Trace:
[<c0396a2c>] ? printk+0xf/0x13
[<c0169ec1>] __alloc_pages_nodemask+0x3dd/0x41f
[<c0106907>] dma_generic_alloc_coherent+0x53/0xb8
[<c01068b4>] ? dma_generic_alloc_coherent+0x0/0xb8
[<e159d12f>] ipw_load_firmware+0x8c/0x4f8 [ipw2200]
[<c01029fc>] ? restore_all_notrace+0x0/0x18
[<e1599e4d>] ? ipw_stop_nic+0x2b/0x5d [ipw2200]
[<e15a194e>] ipw_load+0x8b2/0xf94 [ipw2200]
[<c0399680>] ? _spin_unlock_irqrestore+0x36/0x51
[<e15a57be>] ipw_up+0xe1/0x5c6 [ipw2200]
[<e15a3834>] ? ipw_down+0x1f7/0x1ff [ipw2200]
[<e15a5cd5>] ipw_adapter_restart+0x32/0x46 [ipw2200]
[<e15a5d0a>] ipw_bg_adapter_restart+0x21/0x2c [ipw2200]
[<c0139aac>] worker_thread+0x15e/0x240
[<c0139a6a>] ? worker_thread+0x11c/0x240
[<e15a5ce9>] ? ipw_bg_adapter_restart+0x0/0x2c [ipw2200]
[<c013ce99>] ? autoremove_wake_function+0x0/0x2f
[<c013994e>] ? worker_thread+0x0/0x240
[<c013cc5f>] kthread+0x66/0x6b
[<c013cbf9>] ? kthread+0x0/0x6b
[<c01034eb>] kernel_thread_helper+0x7/0x10
Mem-Info:
DMA per-cpu:
CPU 0: hi: 0, btch: 1 usd: 0
Normal per-cpu:
CPU 0: hi: 186, btch: 31 usd: 178
Active_anon:22467 active_file:10815 inactive_anon:22483
inactive_file:28605 unevictable:2 dirty:626 writeback:190 unstable:0
free:28497 slab:4190 mapped:5638 pagetables:895 bounce:0
DMA free:2084kB min:84kB low:104kB high:124kB active_anon:732kB inactive_anon:996kB active_file:652kB inactive_file:1980kB unevictable:0kB present:15868kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 492 492
Normal free:111904kB min:2792kB low:3488kB high:4188kB active_anon:89136kB inactive_anon:88936kB active_file:42608kB inactive_file:112440kB unevictable:8kB present:503872kB pages_scanned:53 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 9*4kB 4*8kB 6*16kB 2*32kB 1*64kB 0*128kB 1*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 2084kB
Normal: 12926*4kB 2437*8kB 1294*16kB 479*32kB 63*64kB 5*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 111904kB
40160 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 0kB
Total swap = 0kB
131056 pages RAM
3587 pages reserved
50606 pages shared
66006 pages non-shared
ipw2200: Unable to load firmware: -12
ipw2200: Unable to load firmware: -12
ipw2200: Failed to up device
next prev parent reply other threads:[~2009-08-07 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:22 linux-next: Tree for August 6 Stephen Rothwell
2009-08-06 20:50 ` Bartlomiej Zolnierkiewicz
2009-08-07 13:15 ` Bartlomiej Zolnierkiewicz [this message]
2009-08-15 16:56 ` mm/ipw2200 regression (was: Re: linux-next: Tree for August 6) Bartlomiej Zolnierkiewicz
2009-08-15 16:56 ` Bartlomiej Zolnierkiewicz
2009-08-16 7:31 ` Stephen Rothwell
2009-08-16 10:17 ` Bartlomiej Zolnierkiewicz
2009-08-16 10:17 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2010-08-06 3:27 linux-next: Tree for August 6 Stephen Rothwell
2008-08-06 8:28 Stephen Rothwell
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=200908071515.45169.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.