* linux-next: Tree for August 6
@ 2009-08-06 9:22 Stephen Rothwell
2009-08-06 20:50 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 8+ messages in thread
From: Stephen Rothwell @ 2009-08-06 9:22 UTC (permalink / raw)
To: linux-next; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 8479 bytes --]
Hi all,
Changes since 20090805:
The next-yyyymmdd tags will now be signed tags by request.
This tree fails to build for powerpc allyesconfig (final link problem).
The agp tree gained a build failure for which I reverted a commit.
The edac-amd tree lost its conflicts but gained another conflict against
the rr tree.
The tty tree lost a conflict.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES) and i386, sparc and sparc64 defconfig.
These builds also have CONFIG_ENABLE_WARN_DEPRECATED,
CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 138 trees (counting Linus' and 20 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging fixes/fixes
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/tty.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
Merging crypto-current/master
Merging dwmw2/master
Merging arm/devel
CONFLICT (content): Merge conflict in MAINTAINERS
Merging davinci/for-next
Merging pxa/for-next
CONFLICT (content): Merge conflict in MAINTAINERS
Merging thumb-2/thumb-2
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging microblaze/next
Merging mips/mips-for-linux-next
CONFLICT (content): Merge conflict in arch/mips/cavium-octeon/dma-octeon.c
CONFLICT (add/add): Merge conflict in arch/mips/cavium-octeon/executive/cvmx-helper-errata.c
CONFLICT (content): Merge conflict in arch/mips/mm/tlbex.c
CONFLICT (content): Merge conflict in arch/mips/sibyte/swarm/setup.c
CONFLICT (content): Merge conflict in drivers/char/hw_random/Kconfig
CONFLICT (content): Merge conflict in drivers/char/hw_random/Makefile
CONFLICT (add/add): Merge conflict in drivers/dma/txx9dmac.c
Merging parisc/next
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging s390/features
Merging sh/master
Merging sparc/master
Merging xtensa/master
Merging cifs/master
Merging configfs/linux-next
CONFLICT (content): Merge conflict in fs/configfs/dir.c
Merging ecryptfs/next
Merging ext3/for_next
Merging ext4/next
Merging fatfs/master
Merging fuse/for-next
Merging gfs2/master
Merging jfs/next
Merging nfs/linux-next
Merging nfsd/nfsd-next
Merging nilfs2/for-next
Merging ocfs2/linux-next
Merging squashfs/master
Merging v9fs/for-next
Merging ubifs/linux-next
Merging xfs/master
Merging reiserfs-bkl/reiserfs/kill-bkl
Merging vfs/for-next
Merging pci/linux-next
Merging hid/for-next
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/board-dm646x-evm.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/dm355.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/dm644x.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/dm646x.c
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/include/mach/dm355.h
CONFLICT (content): Merge conflict in arch/arm/mach-davinci/include/mach/dm644x.h
Merging quota/for_next
Merging kbuild/master
Merging ide/master
Merging libata/NEXT
Merging infiniband/for-next
Merging acpi/test
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/master
Merging dlm/next
Merging scsi/master
Merging async_tx/next
Merging udf/for_next
Merging net/master
Merging wireless/master
Merging mtd/master
Merging crypto/master
Merging sound/for-next
Merging cpufreq/next
Merging quilt/rr
CONFLICT (content): Merge conflict in arch/x86/lguest/boot.c
CONFLICT (content): Merge conflict in drivers/lguest/page_tables.c
CONFLICT (content): Merge conflict in drivers/virtio/virtio_pci.c
[master c69a397] Revert "cpumask:remove-set_cpus_allowed"
Merging mmc/next
Merging input/next
Merging lsm/for-next
Merging block/for-next
Merging quilt/device-mapper
Merging embedded/master
Merging firmware/master
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging mfd/for-next
CONFLICT (content): Merge conflict in drivers/input/misc/Kconfig
Merging hdlc/hdlc-next
Merging drm/drm-next
CONFLICT (content): Merge conflict in drivers/gpu/drm/drm_crtc.c
Merging voltage/for-next
Merging security-testing/next
Merging lblnet/master
Merging agp/agp-next
Merging uwb/for-upstream
Merging watchdog/master
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
Merging osd/linux-next
Merging jc_docs/docs-next
Merging nommu/master
Merging trivial/for-next
CONFLICT (content): Merge conflict in MAINTAINERS
Merging audit/for-next
Merging omap/for-next
Merging quilt/aoe
Merging suspend/linux-next
Merging bluetooth/master
Merging fsnotify/for-next
Merging irda/for-next
Merging hwlat/for-linus
Merging drbd/drbd
Applying: drbd: fix for removal of blk_queue_stack_limits
Merging kmemleak/kmemleak
Merging tip/auto-latest
CONFLICT (content): Merge conflict in include/linux/rcupdate.h
CONFLICT (content): Merge conflict in kernel/fork.c
Merging oprofile/for-next
Merging edac-amd/for-next
CONFLICT (content): Merge conflict in arch/x86/kernel/smpboot.c
Merging percpu/for-next
CONFLICT (content): Merge conflict in arch/sh/kernel/vmlinux.lds.S
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/perf_counter.c
CONFLICT (content): Merge conflict in drivers/cpufreq/cpufreq_ondemand.c
Merging sfi/sfi-test
Merging asm-generic/next
Merging quilt/driver-core
CONFLICT (content): Merge conflict in init/main.c
Merging quilt/tty
CONFLICT (content): Merge conflict in arch/x86/include/asm/termios.h
Merging quilt/usb
CONFLICT (content): Merge conflict in drivers/usb/gadget/m66592-udc.c
CONFLICT (content): Merge conflict in drivers/usb/host/r8a66597-hcd.c
Merging quilt/staging
CONFLICT (delete/modify): drivers/staging/epl/VirtualEthernetLinux.c deleted in quilt/staging and modified in HEAD. Version HEAD of drivers/staging/epl/VirtualEthernetLinux.c left in tree.
$ git rm -f drivers/staging/epl/VirtualEthernetLinux.c
Merging scsi-post-merge/master
[master 0e15677] Revert "agp: kill phys_to_gart() and gart_to_phys()"
[master c95724f] Revert "agp: Switch agp_{un,}map_page() to take struct page * argument"
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: Tree for August 6
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
0 siblings, 1 reply; 8+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2009-08-06 20:50 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, LKML
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. ]
- bdi warning, http://lkml.org/lkml/2009/7/15/262, (this one goes back
to at least next-20090708, reconfirmed with next-20090806).
- Random OOPSes on shutdown (since the last week or so, didn't have time
to investigate them).
- Lockup on stopping iptables (I've just noticed it in next-20090806,
seems to also happen with next-20090731).
I give up and I'm back to using Linus' tree.. :(
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: Tree for August 6
2009-08-06 20:50 ` Bartlomiej Zolnierkiewicz
@ 2009-08-07 13:15 ` Bartlomiej Zolnierkiewicz
2009-08-15 16:56 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 8+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2009-08-07 13:15 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, LKML
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* mm/ipw2200 regression (was: Re: linux-next: Tree for August 6)
2009-08-07 13:15 ` Bartlomiej Zolnierkiewicz
@ 2009-08-15 16:56 ` Bartlomiej Zolnierkiewicz
0 siblings, 0 replies; 8+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2009-08-15 16:56 UTC (permalink / raw)
To: linux-mm; +Cc: Stephen Rothwell, linux-next, LKML, Rafael J. Wysocki
On Friday 07 August 2009 15:15:45 Bartlomiej Zolnierkiewicz wrote:
> 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
The bug managed to slip into Linus' tree..
ipw2200: Firmware error detected. Restarting.
ipw2200/0: page allocation failure. order:6, mode:0x8020
Pid: 945, comm: ipw2200/0 Not tainted 2.6.31-rc6-dirty #69
Call Trace:
[<c039505f>] ? printk+0xf/0x18
[<c016abc7>] __alloc_pages_nodemask+0x400/0x442
[<c01068b5>] dma_generic_alloc_coherent+0x53/0xc2
[<c0106862>] ? dma_generic_alloc_coherent+0x0/0xc2
[<e12c409b>] ipw_load_firmware+0x8f/0x4fb [ipw2200]
[<c01029bc>] ? restore_all_notrace+0x0/0x18
[<e12c0def>] ? ipw_stop_nic+0x2b/0x5d [ipw2200]
[<e12c88bd>] ipw_load+0x8b2/0xf94 [ipw2200]
[<e12cc727>] ipw_up+0xe1/0x5c6 [ipw2200]
[<e12ca7a3>] ? ipw_down+0x1f7/0x1ff [ipw2200]
[<e12ccc3e>] ipw_adapter_restart+0x32/0x46 [ipw2200]
[<e12ccc73>] ipw_bg_adapter_restart+0x21/0x2c [ipw2200]
[<c0139694>] worker_thread+0x15e/0x240
[<c0139652>] ? worker_thread+0x11c/0x240
[<e12ccc52>] ? ipw_bg_adapter_restart+0x0/0x2c [ipw2200]
[<c013ca65>] ? autoremove_wake_function+0x0/0x2f
[<c0139536>] ? worker_thread+0x0/0x240
[<c013c828>] kthread+0x6b/0x70
[<c013c7bd>] ? kthread+0x0/0x70
[<c01034ab>] 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: 80
Active_anon:25319 active_file:23485 inactive_anon:25576
inactive_file:23530 unevictable:2 dirty:1464 writeback:200 unstable:0
free:11175 slab:6927 mapped:7760 pagetables:930 bounce:0
DMA free:2052kB min:84kB low:104kB high:124kB active_anon:0kB inactive_anon:92kB active_file:1608kB inactive_file:1604kB unevictable:0kB present:15788kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 489 489
Normal free:42648kB min:2788kB low:3484kB high:4180kB active_anon:101276kB inactive_anon:102212kB active_file:92332kB inactive_file:92516kB unevictable:8kB present:501392kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 3*4kB 7*8kB 2*16kB 1*32kB 0*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 2052kB
Normal: 1038*4kB 2148*8kB 1200*16kB 56*32kB 1*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 42648kB
52333 total pagecache pages
4675 pages in swap cache
Swap cache stats: add 27030, delete 22355, find 3967/5275
Free swap = 956380kB
Total swap = 1020116kB
131056 pages RAM
4225 pages reserved
53608 pages shared
86334 pages non-shared
ipw2200: Unable to load firmware: -12
ipw2200: Unable to load firmware: -12
ipw2200: Failed to up device
^ permalink raw reply [flat|nested] 8+ messages in thread
* mm/ipw2200 regression (was: Re: linux-next: Tree for August 6)
@ 2009-08-15 16:56 ` Bartlomiej Zolnierkiewicz
0 siblings, 0 replies; 8+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2009-08-15 16:56 UTC (permalink / raw)
To: linux-mm; +Cc: Stephen Rothwell, linux-next, LKML, Rafael J. Wysocki
On Friday 07 August 2009 15:15:45 Bartlomiej Zolnierkiewicz wrote:
> 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
The bug managed to slip into Linus' tree..
ipw2200: Firmware error detected. Restarting.
ipw2200/0: page allocation failure. order:6, mode:0x8020
Pid: 945, comm: ipw2200/0 Not tainted 2.6.31-rc6-dirty #69
Call Trace:
[<c039505f>] ? printk+0xf/0x18
[<c016abc7>] __alloc_pages_nodemask+0x400/0x442
[<c01068b5>] dma_generic_alloc_coherent+0x53/0xc2
[<c0106862>] ? dma_generic_alloc_coherent+0x0/0xc2
[<e12c409b>] ipw_load_firmware+0x8f/0x4fb [ipw2200]
[<c01029bc>] ? restore_all_notrace+0x0/0x18
[<e12c0def>] ? ipw_stop_nic+0x2b/0x5d [ipw2200]
[<e12c88bd>] ipw_load+0x8b2/0xf94 [ipw2200]
[<e12cc727>] ipw_up+0xe1/0x5c6 [ipw2200]
[<e12ca7a3>] ? ipw_down+0x1f7/0x1ff [ipw2200]
[<e12ccc3e>] ipw_adapter_restart+0x32/0x46 [ipw2200]
[<e12ccc73>] ipw_bg_adapter_restart+0x21/0x2c [ipw2200]
[<c0139694>] worker_thread+0x15e/0x240
[<c0139652>] ? worker_thread+0x11c/0x240
[<e12ccc52>] ? ipw_bg_adapter_restart+0x0/0x2c [ipw2200]
[<c013ca65>] ? autoremove_wake_function+0x0/0x2f
[<c0139536>] ? worker_thread+0x0/0x240
[<c013c828>] kthread+0x6b/0x70
[<c013c7bd>] ? kthread+0x0/0x70
[<c01034ab>] 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: 80
Active_anon:25319 active_file:23485 inactive_anon:25576
inactive_file:23530 unevictable:2 dirty:1464 writeback:200 unstable:0
free:11175 slab:6927 mapped:7760 pagetables:930 bounce:0
DMA free:2052kB min:84kB low:104kB high:124kB active_anon:0kB inactive_anon:92kB active_file:1608kB inactive_file:1604kB unevictable:0kB present:15788kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 489 489
Normal free:42648kB min:2788kB low:3484kB high:4180kB active_anon:101276kB inactive_anon:102212kB active_file:92332kB inactive_file:92516kB unevictable:8kB present:501392kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 3*4kB 7*8kB 2*16kB 1*32kB 0*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 2052kB
Normal: 1038*4kB 2148*8kB 1200*16kB 56*32kB 1*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 42648kB
52333 total pagecache pages
4675 pages in swap cache
Swap cache stats: add 27030, delete 22355, find 3967/5275
Free swap = 956380kB
Total swap = 1020116kB
131056 pages RAM
4225 pages reserved
53608 pages shared
86334 pages non-shared
ipw2200: Unable to load firmware: -12
ipw2200: Unable to load firmware: -12
ipw2200: Failed to up device
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mm/ipw2200 regression (was: Re: linux-next: Tree for August 6)
2009-08-15 16:56 ` Bartlomiej Zolnierkiewicz
(?)
@ 2009-08-16 7:31 ` Stephen Rothwell
2009-08-16 10:17 ` Bartlomiej Zolnierkiewicz
-1 siblings, 1 reply; 8+ messages in thread
From: Stephen Rothwell @ 2009-08-16 7:31 UTC (permalink / raw)
To: Bartlomiej Zolnierkiewicz; +Cc: linux-mm, linux-next, LKML, Rafael J. Wysocki
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi Bart,
On Sat, 15 Aug 2009 18:56:48 +0200 Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
> The bug managed to slip into Linus' tree..
>
> ipw2200: Firmware error detected. Restarting.
> ipw2200/0: page allocation failure. order:6, mode:0x8020
> Pid: 945, comm: ipw2200/0 Not tainted 2.6.31-rc6-dirty #69
^^^^^
So, this is rc6 plus what? (just in case it is relevant).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mm/ipw2200 regression (was: Re: linux-next: Tree for August 6)
2009-08-16 7:31 ` Stephen Rothwell
@ 2009-08-16 10:17 ` Bartlomiej Zolnierkiewicz
0 siblings, 0 replies; 8+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2009-08-16 10:17 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-mm, linux-next, LKML, Rafael J. Wysocki, akpm
Hi,
On Sunday 16 August 2009 09:31:01 Stephen Rothwell wrote:
> Hi Bart,
>
> On Sat, 15 Aug 2009 18:56:48 +0200 Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> >
> > The bug managed to slip into Linus' tree..
> >
> > ipw2200: Firmware error detected. Restarting.
> > ipw2200/0: page allocation failure. order:6, mode:0x8020
> > Pid: 945, comm: ipw2200/0 Not tainted 2.6.31-rc6-dirty #69
> ^^^^^
> So, this is rc6 plus what? (just in case it is relevant).
In this case plus upcoming staging/rt{286,287,307}0 patches (irrelevant,
they are not used on this machine and the problem happened many times
with vanilla -next kernels in the past)..
After going through mm commits in Linus' tree I think that the bug came
the other way around, from akpm's tree to Linus' tree and then to -next
(page allocator changes seem to match "the suspect's profile")..
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: mm/ipw2200 regression (was: Re: linux-next: Tree for August 6)
@ 2009-08-16 10:17 ` Bartlomiej Zolnierkiewicz
0 siblings, 0 replies; 8+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2009-08-16 10:17 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-mm, linux-next, LKML, Rafael J. Wysocki, akpm
Hi,
On Sunday 16 August 2009 09:31:01 Stephen Rothwell wrote:
> Hi Bart,
>
> On Sat, 15 Aug 2009 18:56:48 +0200 Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> >
> > The bug managed to slip into Linus' tree..
> >
> > ipw2200: Firmware error detected. Restarting.
> > ipw2200/0: page allocation failure. order:6, mode:0x8020
> > Pid: 945, comm: ipw2200/0 Not tainted 2.6.31-rc6-dirty #69
> ^^^^^
> So, this is rc6 plus what? (just in case it is relevant).
In this case plus upcoming staging/rt{286,287,307}0 patches (irrelevant,
they are not used on this machine and the problem happened many times
with vanilla -next kernels in the past)..
After going through mm commits in Linus' tree I think that the bug came
the other way around, from akpm's tree to Linus' tree and then to -next
(page allocator changes seem to match "the suspect's profile")..
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2009-08-16 10:18 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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.