Hi all,
Changes since next-20080613:
The driver-core tree gained a conflict with the scsi-rc-fixes tree.
The ide tree needed a build fixup patch.
The net (really the included wireless) tree gained a couple of conflicts
with the wireless-current tree. It also needed a build fixup patch.
The arm tree needed a new driver reverted because it needs better Kconfig
dependencies.
The blk-removal tree gained a conflict with the acpi tree.
The pcmcia tree gained a conflict with the bkl-removal tree.
I have temporarily applied the patch "powerpc: ppc32 does not need
console_drivers exported" to fix know build problems on some powerpc
platforms.
----------------------------------------------------------------------------
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, it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig and i386, sparc and sparc64 defconfig.
Below is a summary of the state of the merge.
We are up to 92 trees (counting Linus' and 13 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 [email protected]
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging powerpc-merge/merge
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sparc-current/master
Merging sound-current/for-linus
Merging arm-current/master
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 quilt/driver-core
CONFLICT (content): Merge conflict in drivers/scsi/hosts.c
Merging quilt/usb
Merging 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
CONFLICT (content): Merge conflict in kernel/Makefile
Applying ftrace: fix rculist split fallout
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
Merging x86/auto-x86-next
CONFLICT (content): Merge conflict in arch/x86/kernel/io_apic_32.c
CONFLICT (delete/modify): arch/x86/kernel/nmi_32.c deleted in x86/auto-x86-next and modified in HEAD. Version HEAD of arch/x86/kernel/nmi_32.c left in tree.
CONFLICT (content): Merge conflict in arch/x86/kernel/process_32.c
CONFLICT (content): Merge conflict in arch/x86/kernel/process_64.c
Merging pci/linux-next
CONFLICT (content): Merge conflict in arch/x86/pci/irq.c
CONFLICT (content): Merge conflict in include/linux/device.h
Merging quilt/device-mapper
Merging hid/mm
Merging quilt/i2c
CONFLICT (content): Merge conflict in drivers/i2c/i2c-core.c
Merging quilt/kernel-doc
Merging avr32/avr32-arch
Merging v4l-dvb/stable
Merging s390/features
CONFLICT (content): Merge conflict in drivers/s390/block/dasd.c
CONFLICT (content): Merge conflict in drivers/s390/block/dasd_eckd.c
CONFLICT (content): Merge conflict in drivers/s390/block/dasd_fba.c
CONFLICT (content): Merge conflict in drivers/s390/char/tape_core.c
CONFLICT (content): Merge conflict in drivers/s390/cio/device_fsm.c
CONFLICT (content): Merge conflict in drivers/s390/net/claw.c
CONFLICT (content): Merge conflict in drivers/s390/net/ctcm_main.c
CONFLICT (content): Merge conflict in drivers/s390/net/lcs.c
Merging sh/master
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Applying ide pmac fixes 1
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
Merging infiniband/for-next
Merging acpi/test
CONFLICT (content): Merge conflict in drivers/acpi/processor_throttling.c
CONFLICT (content): Merge conflict in drivers/acpi/sleep/main.c
Merging blackfin/for-linus
Merging nfsd/nfsd-next
CONFLICT (content): Merge conflict in net/sunrpc/svc.c
Merging ieee1394/for-next
Merging hwmon/testing
Merging ubi/master
Merging kvm/master
Merging dlm/next
Merging scsi/master
Applying scsi: fix fallout from the class_find_device API change
Applying scsi: fix fallout from KOBJ_NAME_LEN removal
Merging ia64/test
Merging tests/master
CONFLICT (content): Merge conflict in lib/Kconfig.debug
Merging ocfs2/linux-next
Merging selinux/for-akpm
Merging quilt/m68k
Merging powerpc/powerpc-next
Merging lblnet/master
Merging ext4/next
Merging 4xx/next
Merging async_tx/next
Merging udf/for_next
Merging security-testing/next
Merging net/master
CONFLICT (content): Merge conflict in Documentation/powerpc/booting-without-of.txt
CONFLICT (content): Merge conflict in drivers/net/wireless/rt2x00/Kconfig
CONFLICT (content): Merge conflict in drivers/net/wireless/rt2x00/rt2x00usb.c
Applying wireless: fix fallout from device_create removal
Merging sparc/master
Merging galak/powerpc-next
CONFLICT (content): Merge conflict in Documentation/powerpc/booting-without-of.txt
Merging mtd/master
Merging wireless/master
Merging crypto/master
Merging vfs/vfs-2.6.25
Merging sound/master
Merging arm/devel
CONFLICT (content): Merge conflict in arch/arm/mach-at91/board-yl-9200.c
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/tosa.c
Created commit dda0dc5: Revert "[ARM] 5096/1: Support Toshiba TC6393XB Mobile I/O Controller."
Merging cpufreq/next
CONFLICT (content): Merge conflict in drivers/cpufreq/cpufreq.c
Merging v9fs/for-next
Merging quilt/rr
Merging cifs/master
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging semaphore-removal/semaphore-removal
CONFLICT (content): Merge conflict in drivers/net/ps3_gelic_wireless.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_attr.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_def.h
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_mbx.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_mid.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_os.c
Merging bkl-removal/bkl-removal
CONFLICT (content): Merge conflict in kernel/power/user.c
Merging trivial/next
Merging ubifs/for_andrew
Merging lsm/for-next
Merging block/for-next
CONFLICT (content): Merge conflict in arch/powerpc/Kconfig
CONFLICT (content): Merge conflict in arch/x86/kernel/apic_32.c
CONFLICT (delete/modify): arch/x86/kernel/i8259_64.c deleted in HEAD and modified in block/for-next. Version block/for-next of arch/x86/kernel/i8259_64.c left in tree.
CONFLICT (content): Merge conflict in arch/x86/xen/smp.c
CONFLICT (delete/modify): include/asm-x86/hw_irq_32.h deleted in HEAD and modified in block/for-next. Version block/for-next of include/asm-x86/hw_irq_32.h left in tree.
CONFLICT (delete/modify): include/asm-x86/hw_irq_64.h deleted in HEAD and modified in block/for-next. Version block/for-next of include/asm-x86/hw_irq_64.h left in tree.
CONFLICT (delete/modify): include/asm-x86/mach-default/irq_vectors.h deleted in HEAD and modified in block/for-next. Version block/for-next of include/asm-x86/mach-default/irq_vectors.h left in tree.
CONFLICT (delete/modify): include/asm-x86/mach-voyager/irq_vectors.h deleted in HEAD and modified in block/for-next. Version block/for-next of include/asm-x86/mach-voyager/irq_vectors.h left in tree.
CONFLICT (content): Merge conflict in kernel/Makefile
Applying block: fix up rculist split fallout
Merging embedded/master
Merging firmware/master
CONFLICT (content): Merge conflict in drivers/char/ip2/ip2main.c
CONFLICT (content): Merge conflict in drivers/usb/misc/isight_firmware.c
CONFLICT (content): Merge conflict in drivers/usb/serial/Kconfig
CONFLICT (delete/modify): drivers/usb/serial/ti_fw_3410.h deleted in firmware/master and modified in HEAD. Version HEAD of drivers/usb/serial/ti_fw_3410.h left in tree.
CONFLICT (delete/modify): drivers/usb/serial/ti_fw_5052.h deleted in firmware/master and modified in HEAD. Version HEAD of drivers/usb/serial/ti_fw_5052.h left in tree.
CONFLICT (content): Merge conflict in drivers/usb/serial/ti_usb_3410_5052.c
CONFLICT (content): Merge conflict in sound/pci/Kconfig
CONFLICT (content): Merge conflict in sound/pci/maestro3.c
CONFLICT (content): Merge conflict in sound/pci/ymfpci/ymfpci_main.c
Merging pcmcia/master
CONFLICT (content): Merge conflict in drivers/char/pcmcia/cm4000_cs.c
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
CONFLICT (content): Merge conflict in drivers/video/backlight/Kconfig
CONFLICT (content): Merge conflict in drivers/video/backlight/Makefile
Merging kgdb/kgdb-next
Applying powerpc: ppc32 does not need console_drivers exported
Am Montag, den 16.06.2008, 19:01 +1000 schrieb Stephen Rothwell:
> Changes since next-20080613:
>
> The driver-core tree gained a conflict with the scsi-rc-fixes tree.
>
> The ide tree needed a build fixup patch.
>
> The net (really the included wireless) tree gained a couple of conflicts
> with the wireless-current tree. It also needed a build fixup patch.
>
> The arm tree needed a new driver reverted because it needs better Kconfig
> dependencies.
>
> The blk-removal tree gained a conflict with the acpi tree.
>
> The pcmcia tree gained a conflict with the bkl-removal tree.
>
> I have temporarily applied the patch "powerpc: ppc32 does not need
> console_drivers exported" to fix know build problems on some powerpc
> platforms.
My internet is gone :-(
[ 24.176830] kernel BUG at kernel/workqueue.c:169!
[ 24.176830] invalid opcode: 0000 [#1] SMP
[ 24.176830] last sysfs file: /sys/devices/pci0000:00/0000:00:05.0/host2/target2:0:0/2:0:0:0/rev
[ 24.176830] Modules linked in: rndis_wlan(+) cfi_probe snd_pcm gen_probe rndis_host ck804xrom(+) cdc_ether mtd snd_timer usbnet snd_page_alloc chipreg k8temp(+) snd_hwdep i2c_nforce2(+) hwmon button snd forcedeth(+) mii map_funcs i2c_core serio_raw soundcore pcspkr sg sr_mod cdrom sata_nv pata_amd ata_generic pata_acpi libata sd_mod scsi_mod sha256_generic aes_i586 dm_crypt dm_snapshot dm_zero dm_mirror dm_log dm_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan]
[ 24.176830]
[ 24.176830] Pid: 1006, comm: modprobe Not tainted (2.6.26-rc6-next-20080616 #74)
[ 24.176830] EIP: 0060:[<c04342e4>] EFLAGS: 00010213 CPU: 0
[ 24.176830] EIP is at queue_work+0x1b/0x48
[ 24.176830] EAX: f786606c EBX: 00000000 ECX: 00000000 EDX: f7866068
[ 24.176830] ESI: f7866800 EDI: f897a98c EBP: f6490c88 ESP: f6490c84
[ 24.176830] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 24.176830] Process modprobe (pid: 1006, ti=f6490000 task=f6458c70 task.ti=f6490000)
[ 24.176830] Stack: f6e93cb8 f6490c90 f99a00b1 f6490cc0 f897a343 f7865c80 f7865d50 00000000
[ 24.176830] 00000000 80000002 00000001 00000000 00000003 ffffffea f7865c80 f6490d00
[ 24.176830] f897a625 00000001 00000002 f6e93c00 f7865c80 f7865800 f7866800 c04f6d22
[ 24.176830] Call Trace:
[ 24.176830] [<f99a00b1>] ? rndis_wext_link_change+0x29/0x2b [rndis_wlan]
[ 24.176830] [<f897a343>] ? rndis_command+0x1af/0x23c [rndis_host]
[ 24.176830] [<f897a625>] ? generic_rndis_bind+0x109/0x3a6 [rndis_host]
[ 24.176830] [<c04f6d22>] ? idr_get_empty_slot+0x12a/0x1d9
[ 24.176830] [<f99a1f9f>] ? rndis_wext_bind+0x74/0x289 [rndis_wlan]
[ 24.176830] [<c05be14e>] ? alloc_netdev_mq+0xb8/0xc3
[ 24.176830] [<c05cbc0d>] ? ether_setup+0x0/0x78
[ 24.176830] [<f89685b3>] ? usbnet_probe+0x21d/0x4dd [usbnet]
[ 24.176830] [<c062ddfb>] ? mutex_lock+0x1d/0x2d
[ 24.176830] [<c0581ab5>] ? usb_autopm_do_device+0xb1/0xb9
[ 24.176830] [<c0582081>] ? usb_probe_interface+0xbc/0xef
[ 24.176830] [<c056bc6d>] ? driver_probe_device+0xa0/0x136
[ 24.176830] [<c056bd3d>] ? __driver_attach+0x3a/0x59
[ 24.176830] [<c056b6a5>] ? bus_for_each_dev+0x3b/0x63
[ 24.176830] [<c056bb12>] ? driver_attach+0x14/0x16
[ 24.176830] [<c056bd03>] ? __driver_attach+0x0/0x59
[ 24.176830] [<c056b0da>] ? bus_add_driver+0x9d/0x1ba
[ 24.176830] [<c056bec7>] ? driver_register+0x81/0xe1
[ 24.176830] [<c0582266>] ? usb_register_driver+0x66/0xc0
[ 24.176830] [<f891d017>] ? rndis_wlan_init+0x17/0x19 [rndis_wlan]
[ 24.176830] [<c04451bb>] ? sys_init_module+0x177e/0x1930
[ 24.176830] [<c0403895>] ? sysenter_past_esp+0x6a/0x91
[ 24.176830] =======================
[ 24.176830] Code: 76 c0 8b 00 f7 d0 8b 04 88 e8 a7 ff ff ff c9 c3 55 89 e5 53 89 c3 f0 0f ba 2a 00 19 c0 31 c9 85 c0 75 30 8d 42 04 39 42 04 74 04 <0f> 0b eb fe 64 8b 0d 04 00 7b c0 83 7b 10 00 74 06 8b 0d f4 b4
[ 24.176830] EIP: [<c04342e4>] queue_work+0x1b/0x48 SS:ESP 0068:f6490c84
[ 24.185309] ---[ end trace 6a99273b07870aed ]---
See attached dmesg and config.
greets
thomas
Am Montag, den 16.06.2008, 23:28 +0200 schrieb Thomas Meyer:
> My internet is gone :-(
>
> [ 24.176830] kernel BUG at kernel/workqueue.c:169!
> [ 24.176830] invalid opcode: 0000 [#1] SMP
> [ 24.176830] last sysfs file: /sys/devices/pci0000:00/0000:00:05.0/host2/target2:0:0/2:0:0:0/rev
> [ 24.176830] Modules linked in: rndis_wlan(+) cfi_probe snd_pcm gen_probe rndis_host ck804xrom(+) cdc_ether mtd snd_timer usbnet snd_page_alloc chipreg k8temp(+) snd_hwdep i2c_nforce2(+) hwmon button snd forcedeth(+) mii map_funcs i2c_core serio_raw soundcore pcspkr sg sr_mod cdrom sata_nv pata_amd ata_generic pata_acpi libata sd_mod scsi_mod sha256_generic aes_i586 dm_crypt dm_snapshot dm_zero dm_mirror dm_log dm_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan]
> [ 24.176830]
> [ 24.176830] Pid: 1006, comm: modprobe Not tainted (2.6.26-rc6-next-20080616 #74)
> [ 24.176830] EIP: 0060:[<c04342e4>] EFLAGS: 00010213 CPU: 0
> [ 24.176830] EIP is at queue_work+0x1b/0x48
> [ 24.176830] EAX: f786606c EBX: 00000000 ECX: 00000000 EDX: f7866068
> [ 24.176830] ESI: f7866800 EDI: f897a98c EBP: f6490c88 ESP: f6490c84
> [ 24.176830] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> [ 24.176830] Process modprobe (pid: 1006, ti=f6490000 task=f6458c70 task.ti=f6490000)
> [ 24.176830] Stack: f6e93cb8 f6490c90 f99a00b1 f6490cc0 f897a343 f7865c80 f7865d50 00000000
> [ 24.176830] 00000000 80000002 00000001 00000000 00000003 ffffffea f7865c80 f6490d00
> [ 24.176830] f897a625 00000001 00000002 f6e93c00 f7865c80 f7865800 f7866800 c04f6d22
> [ 24.176830] Call Trace:
> [ 24.176830] [<f99a00b1>] ? rndis_wext_link_change+0x29/0x2b [rndis_wlan]
> [ 24.176830] [<f897a343>] ? rndis_command+0x1af/0x23c [rndis_host]
> [ 24.176830] [<f897a625>] ? generic_rndis_bind+0x109/0x3a6 [rndis_host]
> [ 24.176830] [<c04f6d22>] ? idr_get_empty_slot+0x12a/0x1d9
> [ 24.176830] [<f99a1f9f>] ? rndis_wext_bind+0x74/0x289 [rndis_wlan]
> [ 24.176830] [<c05be14e>] ? alloc_netdev_mq+0xb8/0xc3
> [ 24.176830] [<c05cbc0d>] ? ether_setup+0x0/0x78
> [ 24.176830] [<f89685b3>] ? usbnet_probe+0x21d/0x4dd [usbnet]
> [ 24.176830] [<c062ddfb>] ? mutex_lock+0x1d/0x2d
> [ 24.176830] [<c0581ab5>] ? usb_autopm_do_device+0xb1/0xb9
> [ 24.176830] [<c0582081>] ? usb_probe_interface+0xbc/0xef
> [ 24.176830] [<c056bc6d>] ? driver_probe_device+0xa0/0x136
> [ 24.176830] [<c056bd3d>] ? __driver_attach+0x3a/0x59
> [ 24.176830] [<c056b6a5>] ? bus_for_each_dev+0x3b/0x63
> [ 24.176830] [<c056bb12>] ? driver_attach+0x14/0x16
> [ 24.176830] [<c056bd03>] ? __driver_attach+0x0/0x59
> [ 24.176830] [<c056b0da>] ? bus_add_driver+0x9d/0x1ba
> [ 24.176830] [<c056bec7>] ? driver_register+0x81/0xe1
> [ 24.176830] [<c0582266>] ? usb_register_driver+0x66/0xc0
> [ 24.176830] [<f891d017>] ? rndis_wlan_init+0x17/0x19 [rndis_wlan]
> [ 24.176830] [<c04451bb>] ? sys_init_module+0x177e/0x1930
> [ 24.176830] [<c0403895>] ? sysenter_past_esp+0x6a/0x91
> [ 24.176830] =======================
> [ 24.176830] Code: 76 c0 8b 00 f7 d0 8b 04 88 e8 a7 ff ff ff c9 c3 55 89 e5 53 89 c3 f0 0f ba 2a 00 19 c0 31 c9 85 c0 75 30 8d 42 04 39 42 04 74 04 <0f> 0b eb fe 64 8b 0d 04 00 7b c0 83 7b 10 00 74 06 8b 0d f4 b4
> [ 24.176830] EIP: [<c04342e4>] queue_work+0x1b/0x48 SS:ESP 0068:f6490c84
> [ 24.185309] ---[ end trace 6a99273b07870aed ]---
>
I tried to bisect this one, but without a consistent result. So I looked
at the last changes on the file drivers/net/wireless/rndis_wlan*
Strangley reverting commmit 5720508d9ad9a82927875252b7a19ba2b45f11f8
(rndis_wlan: Use kernel-supplied ARRAY_SIZE() macro) brought back my usb
wlan device!
This is strange, the commit looks good.
Another thing i tried is to change <linux/kernel.h>:
diff --git a/include/linux/kernel.h b/include/linux/kernel.h
index 9453483..fcd7b73 100644
--- a/include/linux/kernel.h
+++ b/include/linux/kernel.h
@@ -40,7 +40,7 @@ extern const char linux_proc_banner[];
#define PTR_ALIGN(p, a) ((typeof(p))ALIGN((unsigned long)(p), (a)))
#define IS_ALIGNED(x, a) (((x) & ((typeof(x))(a) - 1)) == 0)
-#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
+#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]))
#define FIELD_SIZEOF(t, f) (sizeof(((t*)0)->f))
#define DIV_ROUND_UP(n,d) (((n) + (d) - 1) / (d))
Recompling rndis_wlan with above change, makes my usb wlan stick work
again.
Maybe I'm totally wrong here, but i assume that the must_be_array thing
is broken. but OTOH ARRAY_SIZE is used in a lot of places in the kernel.
So I'm not sure what's going on here.
gcc version is:
$ gcc --version
gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)
Feedback msot welcome!
greets
thomas
On Saturday 21 June 2008 04:48:37 Thomas Meyer wrote:
> I tried to bisect this one, but without a consistent result.
That's always suspicious...
> Another thing i tried is to change <linux/kernel.h>:
This will also cause almost everything to be rebuilt. I find it hard to
believe this is the culprit; does a "make clean" also fix it?
Thanks,
Rusty.
Zitat von Rusty Russell <[email protected]>:
> On Saturday 21 June 2008 04:48:37 Thomas Meyer wrote:
> > I tried to bisect this one, but without a consistent result.
>
> That's always suspicious...
>
> > Another thing i tried is to change <linux/kernel.h>:
>
> This will also cause almost everything to be rebuilt. I find it hard to
> believe this is the culprit; does a "make clean" also fix it?
>
Sorry! I compared the created binary and both are equal. So above commit
revertion or the change of linux/kernel.h has nothing to do with the non
working usb wlan stick.
Sometimes it works, sometimes not. And when it's non-working then i also get the
BUG at kernel/workqueue in my dmesg.
Sorry for all the bustle.
greets
thomas