linux-next: Tree for December 31

linux-next: Tree for December 31

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 8737 bytes --]

Hi all,

Changes since 20081230:

Dropped trees (temporarily):
	driver-core (build problem)
	usb (depends on driver-core)
	kvm (build problem)
	semaphore-removal (due to unfixed conflicts against Linus' tree)
	cpu_alloc (build problem)
	audit (difficult conflicts)
	staging (depends on usb)

I substituted a fix commit from the infiniband tree for the revert build
fix for Linus' tree.

The xfs tree lost its 4 conflicts.

The scsi tree lost its build failure.

The firmware tree lost 3 conflicts (because the conflicting commits were
removed from the scsi tree).

----------------------------------------------------------------------------

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,
44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES) and
i386, sparc and sparc64 defconfig.

Below is a summary of the state of the merge.

We are up to 132 trees (counting Linus' and 15 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 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/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
CONFLICT (content): Merge conflict in drivers/char/tty_audit.c
Created commit 309ba8e: Merge commit 'audit-current/for-linus'
Merging dwmw2/master
$ git cherry-pick 2c4ab6243f91cda62f22af2eb8a6c07590de37b1
Created commit 7c453f0: RDMA/addr: Fix build breakage when IPv6 is disabled
Merging arm/devel
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging mips/mips-for-linux-next
Merging parisc/master
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging pxa/for-next
Merging s390/features
Merging sh/master
Merging sparc/master
Merging x86/auto-x86-next
Merging xtensa/master
Merging tip-core/auto-core-next
CONFLICT (content): Merge conflict in include/linux/hardirq.h
Created commit 6620d2d: Merge commit 'tip-core/auto-core-next'
Merging cpus4096/auto-cpus4096-next
Merging ftrace/auto-ftrace-next
Merging genirq/auto-genirq-next
Merging safe-poison-pointers/auto-safe-poison-pointers-next
Merging sched/auto-sched-next
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
CONFLICT (content): Merge conflict in kernel/time/tick-sched.c
Created commit b665237: Merge commit 'timers/auto-timers-next'
Merging pci/linux-next
Merging quilt/device-mapper
CONFLICT (content): Merge conflict in drivers/md/dm.c
Created commit 7afc9a5: Merge branch 'quilt/device-mapper'
Merging hid/for-next
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
Merging infiniband/for-next
Merging acpi/test
Merging nfsd/nfsd-next
CONFLICT (content): Merge conflict in fs/lockd/host.c
CONFLICT (content): Merge conflict in fs/lockd/mon.c
Created commit ff8ad19: Merge commit 'nfsd/nfsd-next'
Merging ieee1394/for-next
Merging ubi/linux-next
Merging dlm/next
Merging scsi/master
Merging ocfs2/linux-next
CONFLICT (content): Merge conflict in fs/ocfs2/namei.c
Created commit 41d1404: Merge commit 'ocfs2/linux-next'
Merging ext4/next
Merging async_tx/next
Applying: net: async_tx merge fix
Created commit 74129d6: Merge commit 'async_tx/next'
Merging udf/for_next
Merging net/master
Merging mtd/master
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/corgi.c
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/poodle.c
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/spitz.c
Created commit 8b5bb2a: Merge commit 'mtd/master'
Merging wireless/master
Merging crypto/master
Merging vfs/for-next
Merging sound/for-next
Merging cpufreq/next
Merging v9fs/for-next
Merging rr_cpumask/master
CONFLICT (content): Merge conflict in kernel/sched.c
Created commit 1653d97: Merge commit 'rr_cpumask/master'
Merging quilt/rr
CONFLICT (content): Merge conflict in kernel/rcuclassic.c
Created commit a788be2: Merge branch 'quilt/rr'
Merging cifs/master
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging bkl-removal/bkl-removal
CONFLICT (content): Merge conflict in fs/ioctl.c
Created commit 28240e8: Merge commit 'bkl-removal/bkl-removal'
Merging ubifs/linux-next
Merging lsm/for-next
Merging block/for-next
Merging embedded/master
Merging firmware/master
CONFLICT (content): Merge conflict in drivers/net/tg3.c
CONFLICT (content): Merge conflict in firmware/Makefile
CONFLICT (content): Merge conflict in firmware/WHENCE
Created commit b64483f: Merge commit '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 kmemcheck/auto-kmemcheck-next
CONFLICT (content): Merge conflict in arch/x86/mm/Makefile
CONFLICT (content): Merge conflict in mm/Makefile
CONFLICT (content): Merge conflict in mm/slub.c
Created commit 6e893bf: Merge commit 'kmemcheck/auto-kmemcheck-next'
Merging generic-ipi/auto-generic-ipi-next
Merging mfd/for-next
Merging hdlc/hdlc-next
Merging drm/drm-next
Merging voltage/for-next
Merging security-testing/next
Merging lblnet/master
CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt
Created commit 0463080: Merge commit 'lblnet/master'
Merging quilt/ttydev
CONFLICT (content): Merge conflict in fs/devpts/inode.c
Created commit e078ab9: Merge branch 'quilt/ttydev'
Merging agp/agp-next
Merging oprofile/auto-oprofile-next
Merging fastboot/auto-fastboot-next
Merging sparseirq/auto-sparseirq-next
Merging iommu/auto-iommu-next
Merging uwb/for-upstream
CONFLICT (content): Merge conflict in drivers/uwb/wlp/eda.c
Created commit 3c3975b: Merge commit 'uwb/for-upstream'
Merging watchdog/master
Merging proc/proc
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
CONFLICT (content): Merge conflict in kernel/sched.c
Created commit db8f43b: Merge commit 'cputime/cputime'
Merging osd/linux-next
Merging fatfs/master
Merging fuse/for-next
Merging jc_docs/docs-next
Merging nommu/master
CONFLICT (content): Merge conflict in kernel/fork.c
Created commit fd70d10: Merge commit 'nommu/master'
Merging boot-params/master
CONFLICT (content): Merge conflict in arch/arm/kernel/setup.c
CONFLICT (content): Merge conflict in arch/parisc/kernel/setup.c
CONFLICT (content): Merge conflict in arch/sh/boards/mach-microdev/setup.c
CONFLICT (content): Merge conflict in arch/sh/boards/mach-migor/setup.c
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/common.c
Created commit 45ff2be: Merge commit 'boot-params/master'
Merging trivial/for-next

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

[BUG] next-20081231 - S390x kernel panics while bootup at init_sched_build_groups()

[Kamalesh Babulal]

Hi,

	next-2001231 kernel panic's on S390x box, while boot up

Linux version 2.6.28-next-20081231-autotest (root@lnxabat1) (gcc version 4.1.0 (
SUSE Linux)) #1 SMP Wed Dec 31 08:43:37 CST 2008
setup: Linux is running as a z/VM guest operating system in 64-bit mode
Zone PFN ranges:
  DMA      0x00000000 -> 0x00080000
  Normal   0x00080000 -> 0x00080000
Movable zone start PFN for each node
early_node_mapÝ1¨ active PFN ranges
    0: 0x00000000 -> 0x00040000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 258560
Kernel command line: root=/dev/dasdc1 selinux=0 IDENT=1230735656 BOOT_IMAGE=0
PID hash table entries: 4096 (order: 12, 32768 bytes)
console ÝttyS0¨ enabled
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 1015808k/1048576k available (2483k kernel code, 0k reserved, 1372k data,
 196k init)
Write protected kernel read-only data: 0x12000 - 0x382fff
SLUB: Genslabs=12, HWalign=256, Order=0-3, MinObjects=0, CPUs=64, Nodes=1
Security Framework initialized
SELinux:  Disabled at boot.
Mount-cache hash table entries: 256
cpu: 4 configured CPUs, 0 standby CPUs
cpu: Processor 0 started, address 2, identification 20AB8A
cpu: Processor 1 started, address 0, identification 00AB8A
cpu: Processor 2 started, address 1, identification 10AB8A
cpu: Processor 3 started, address 3, identification 30AB8A
Brought up 4 CPUs
Unable to handle kernel pointer dereference at virtual kernel address 0000000100
3fa000
Oops: 003b Ý#1¨ SMP
Modules linked in:
CPU: 0 Not tainted 2.6.28-next-20081231-autotest #1
Process swapper (pid: 1, task: 000000003fe80000, ksp: 000000003fe8ba78)
Krnl PSW : 0704000180000000 0000000000035632 (init_sched_build_groups+0xae/0x4a4
)
           R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:0 PM:0 EA:3
Krnl GPRS: 00000000003c27b0 00000001003fa278 0000000000000000 00000000003c2508
           0000000000000000 000000000026f818 0000000000000000 0000000000000000
           0000000000000000 000000003fe8be50 00000000ffffffff 000000003fe8bcf0
Krnl Code: 0000000000035626: a7290000           lghi    00: HCPGSP2629I The virt
ual machine is placed in CP mode due to a SIGP stop from
 CPU 02.
01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from
 CPU 02.
03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from
 CPU 02.
02: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 00021416-- 0:conmux-control -- time-stamp -- Dec/31/08  7:04:54 --
-- 0:conmux-control -- time-stamp -- Dec/31/08  7:22:18 --
(bot:conmon-payload) disconnected
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

[BUG] next-20081231 -powerpc - panic at tasklet_kill_immediate()

[Kamalesh Babulal]

Hi Stephen,

	next-20081231 kernel panic's, while booting up on powerpc. This
panic was visible in next-20081230 kernel also.

[    1.268844] Brought up 2 CPUs
[    1.268873] Unable to handle kernel paging request for data at address 0x00000009
[    1.268876] Faulting instruction address: 0xc00000000005a9f8
[    1.268880] Oops: Kernel access of bad area, sig: 11 [#1]
[    1.268882] SMP NR_CPUS=32 NUMA PowerMac
[    1.268886] Modules linked in:
[    1.268889] NIP: c00000000005a9f8 LR: c00000000006ee54 CTR: c00000000005a9c0
[    1.268893] REGS: c0000002763c3c80 TRAP: 0300   Not tainted  (2.6.28-next-20081231-autokern1)
[    1.268896] MSR: 9000000000009032 <EE,ME,IR,DR>  CR: 24000024  XER: 000fffff
[    1.268903] DAR: 0000000000000009, DSISR: 0000000040000000
[    1.268905] TASK = c0000002760e20c0[5] 'ksoftirqd/1' THREAD: c0000002763c0000 CPU: 1
[    1.268908] GPR00: 0000000000000000 c0000002763c3f00 c0000000004f9088 0000000000000001 
[    1.268913] GPR04: c0000002760e28d0 0000000000000000 0000000024000022 c000000000010098 
[    1.268917] GPR08: 0000000000000000 000000000ec1c518 c000000000514a40 0000000000000010 
[    1.268922] GPR12: c00000000051c700 c00000000051c500 0000000000000000 0000000000000000 
[    1.268926] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
[    1.268930] GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000001400000 
[    1.268934] GPR24: 0000000001829d88 c000000000429b28 0000000001400000 0000000000000000 
[    1.268939] GPR28: c0000002760bfc48 0000000000000001 c000000000498a98 c0000000004b0150 
[    1.268950] NIP [c00000000005a9f8] .tasklet_kill_immediate+0x38/0xb8
[    1.268955] LR [c00000000006ee54] .kthread+0x78/0xc4
[    1.268957] Call Trace:
[    1.268960] [c0000002763c3f00] [c00000000006ee1c] .kthread+0x40/0xc4 (unreliable)
[    1.268967] [c0000002763c3f90] [c0000000000227a8] .kernel_thread+0x54/0x70
[    1.268969] Instruction dump:
[    1.268971] 7c8b07b4 7d693670 7d290194 556b06be e95e8040 7d2907b4 79291f24 e94a0000 
[    1.268977] 7c0a482a 7c005c36 780007e0 0b000000 <e8030008> 7800ffe2 0b000000 e8030008 
[    1.268992] ---[ end trace 31fd0ba7d8756001 ]---
[    1.269016] Unable to handle kernel paging request for data at address 0x00000000
[    1.269019] Faulting instruction address: 0xc0000000000d9b4c
[    1.269022] Oops: Kernel access of bad area, sig: 11 [#2]
[    1.269024] SMP NR_CPUS=32 NUMA PowerMac
[    1.269026] Modules linked in:
[    1.269029] NIP: c0000000000d9b4c LR: c0000000000511fc CTR: 0000000000000003
[    1.269032] REGS: c0000002763c35d0 TRAP: 0300   Tainted: G      D     (2.6.28-next-20081231-autokern1)
[    1.269035] MSR: 9000000000009032 <EE,ME,IR,DR>  CR: 28004082  XER: 200fffff
[    1.269040] DAR: 0000000000000000, DSISR: 0000000040000000
[    1.269043] TASK = c0000002760e20c0[5] 'ksoftirqd/1' THREAD: c0000002763c0000 CPU: 1
[    1.269046] GPR00: 0000000000000004 c0000002763c3850 c0000000004f9088 c000000276027d00 
[    1.269051] GPR04: c0000002763b6980 0000000000000000 c000000000457278 c000000000457278 
[    1.269055] GPR08: c0000002760e2290 0000000000000000 c00000000051c500 c0000002763b6080 
[    1.269060] GPR12: 0000000048000084 c00000000051c500 0000000000000000 0000000000000000 
[    1.269064] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
[    1.269068] GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000001 
[    1.269073] GPR24: c0000002760e20b0 c0000002760e2228 0000000000000000 c000000276027d00 
[    1.269077] GPR28: 0000000000000000 c0000002763b6980 c00000000049c9b8 0000000000000000 
[    1.269086] NIP [c0000000000d9b4c] .kmem_cache_free+0x1b8/0x244
[    1.269090] LR [c0000000000511fc] .__cleanup_sighand+0x44/0x5c
[    1.269092] Call Trace:
[    1.269095] [c0000002763c3850] [c00000000049abe8] 0xc00000000049abe8 (unreliable)
[    1.269099] [c0000002763c3900] [c0000000000511fc] .__cleanup_sighand+0x44/0x5c
[    1.269104] [c0000002763c3980] [c000000000057244] .release_task+0x2dc/0x400
[    1.269108] [c0000002763c3a20] [c000000000057b14] .do_exit+0x7ac/0x858
[    1.269112] [c0000002763c3af0] [c000000000020414] .die+0x1c8/0x1cc
[    1.269117] [c0000002763c3b90] [c000000000027f4c] .bad_page_fault+0xb8/0xd4
[    1.269122] [c0000002763c3c10] [c000000000005318] handle_page_fault+0x3c/0x5c
[    1.269128] --- Exception: 300 at .tasklet_kill_immediate+0x38/0xb8
[    1.269130]     LR = .kthread+0x78/0xc4
[    1.269133] [c0000002763c3f00] [c00000000006ee1c] .kthread+0x40/0xc4 (unreliable)
[    1.269138] [c0000002763c3f90] [c0000000000227a8] .kernel_thread+0x54/0x70
[    1.269141] Instruction dump:
[    1.269142] 4800016d e97d0168 880d01dc 2fa00000 41be0010 7c0004ac 38000000 980d01dc 
[    1.269148] 7c2004ac 38000000 900b0040 48000050 <817f0000> 801f0004 7f8b0040 409c001c 
[    1.269155] ---[ end trace 31fd0ba7d8756001 ]---
[    1.269157] Fixing recursive fault but reboot is needed!
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

Re: [BUG] next-20081231 - S390x kernel panics while bootup at init_sched_build_groups()

[Heiko Carstens]

On Wed, Dec 31, 2008 at 09:33:29PM +0530, Kamalesh Babulal wrote:
> 	next-2001231 kernel panic's on S390x box, while boot up
> cpu: 4 configured CPUs, 0 standby CPUs
> cpu: Processor 0 started, address 2, identification 20AB8A
> cpu: Processor 1 started, address 0, identification 00AB8A
> cpu: Processor 2 started, address 1, identification 10AB8A
> cpu: Processor 3 started, address 3, identification 30AB8A
> Brought up 4 CPUs
> Unable to handle kernel pointer dereference at virtual kernel address 0000000100
> 3fa000
> Oops: 003b Ý#1¨ SMP
> Modules linked in:
> CPU: 0 Not tainted 2.6.28-next-20081231-autotest #1
> Process swapper (pid: 1, task: 000000003fe80000, ksp: 000000003fe8ba78)
> Krnl PSW : 0704000180000000 0000000000035632 (init_sched_build_groups+0xae/0x4a4
> )
>            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:0 PM:0 EA:3
> Krnl GPRS: 00000000003c27b0 00000001003fa278 0000000000000000 00000000003c2508
>            0000000000000000 000000000026f818 0000000000000000 0000000000000000
>            0000000000000000 000000003fe8be50 00000000ffffffff 000000003fe8bcf0
> Krnl Code: 0000000000035626: a7290000           lghi    00: HCPGSP2629I The virt

Seems to be fixed with linux-next from 2nd of January.