linux-next: Tree for May 19 - Kernel

This is a discussion on linux-next: Tree for May 19 - Kernel ; Hi all, News: I will stop making full tar balls tomorrow unless someone screams. The LATEST file now contains the name of the version that the patches are based on i.e. today, LATEST-IS-next-20080519 contains "v2.6.26-rc3". Changes since next-20080516: New tree: ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: linux-next: Tree for May 19

  1. linux-next: Tree for May 19

    Hi all,

    News:
    I will stop making full tar balls tomorrow unless someone screams.
    The LATEST file now contains the name of the version that the
    patches are based on i.e. today, LATEST-IS-next-20080519 contains "v2.6.26-rc3".

    Changes since next-20080516:

    New tree: bkl-removal (this is Jonathan Corbet's tree)

    Removed trees: x86-fixes, sched-fixes (I don't know where they are
    currently).

    Changed trees: x86 and sched are now the new auto merged trees.

    The i2c trivial conflict has moved to the driver-core tree.

    The x86, pci and i2c trees gained a conflict each.

    The cpufreq tree gained three conflicts.

    The rr tree gained a couple of conflicts with the x86 tree.

    The semaphore-removal tree still needed three patches reverted because similar
    patches were merged into upstream and the scsi-rc-fixes trees.

    The bkl-removal tree needed a build fixup patch for viotape.

    I have applied the following temporary patches for known build problems:

    "Fix various 8390 builds" - the net tree broke builds on various
    architectures - hopefully this patch will go into the net tree shortly.

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

    I have created today's linux-next tree at
    git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
    (tar balls and patches at
    http://www.kernel.org/pub/linux/kern...fr/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 73 trees (counting Linus' and 11 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 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 quilt/driver-core
    CONFLICT (content): Merge conflict in arch/powerpc/platforms/pasemi/misc.c
    CONFLICT (content): Merge conflict in include/linux/i2c.h
    Merging quilt/usb
    Merging x86/auto-x86-next
    CONFLICT (content): Merge conflict in kernel/power/main.c
    Merging sched/auto-sched-next
    Merging pci/linux-next
    CONFLICT (content): Merge conflict in drivers/pci/pci-driver.c
    Merging quilt/device-mapper
    Merging hid/mm
    Merging quilt/i2c
    CONFLICT (content): Merge conflict in drivers/i2c/busses/i2c-nforce2.c
    Merging quilt/kernel-doc
    Merging avr32/avr32-arch
    Merging v4l-dvb/stable
    Merging s390/features
    Merging sh/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 blackfin/for-linus
    Merging nfsd/nfsd-next
    Merging ieee1394/for-next
    Merging hwmon/testing
    Merging ubi/master
    Merging kvm/master
    Merging dlm/next
    Merging scsi/master
    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 hrt/mm
    Merging lblnet/master
    Merging ext4/next
    Merging 4xx/next
    Merging async_tx/next
    Merging udf/for_next
    Merging security-testing/next
    Merging net/master
    Merging sparc/master
    Merging galak/powerpc-next
    Merging mtd/master
    Merging wireless/master
    Merging crypto/master
    Merging vfs/vfs-2.6.25
    Merging sound/master
    Merging arm/devel
    Merging cpufreq/master
    CONFLICT (delete/modify): arch/x86/kernel/cpu/cpufreq/p4-clockmod.c deletedin cpufreq/master and modified in HEAD. Version HEAD of arch/x86/kernel/cpu/cpufreq/p4-clockmod.c left in tree.
    CONFLICT (delete/modify): arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c deleted in cpufreq/master and modified in HEAD. Version HEAD of arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c left in tree.
    CONFLICT (content): Merge conflict in drivers/cpufreq/cpufreq.c
    $ git rm arch/x86/kernel/cpu/cpufreq/p4-clockmod.c arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c
    Merging v9fs/for-next
    Merging quilt/rr
    CONFLICT (content): Merge conflict in include/linux/stop_machine.h
    CONFLICT (content): Merge conflict in kernel/stop_machine.c
    Merging cifs/master
    Merging mmc/next
    Merging gfs2/master
    Merging semaphore/semaphore
    Merging semaphore-removal/semaphore-removal
    CONFLICT (content): Merge conflict in drivers/atm/ambassador.c
    CONFLICT (content): Merge conflict in drivers/net/bonding/bond_main.c
    CONFLICT (content): Merge conflict in drivers/net/bonding/bond_sysfs.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
    CONFLICT (content): Merge conflict in net/9p/trans_virtio.c
    $ git reset --hard
    $ git checkout -b tmp semaphore-removal/semaphore-removal
    Created commit d1a82dd: Revert "Convert qla_os to use mutex instead of semaphore"
    Created commit 028419e: Revert "9p: Convert from semaphore to spinlock"
    Created commit 68e79ef: Revert "qla2xxx: Turn vport_sem into vport_mutex"
    $ git checkout master
    CONFLICT (content): Merge conflict in drivers/atm/ambassador.c
    CONFLICT (content): Merge conflict in drivers/net/bonding/bond_main.c
    CONFLICT (content): Merge conflict in drivers/net/bonding/bond_sysfs.c
    Merging quilt/ldp.next
    Merging bkl-removal/bkl-removal
    Applying bkl-removal viotape fixup
    Applying Fix various 8390 builds

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIMS8lTgG2atn1QN8RAuvYAJ46e5CtLT0On6u2SomR+d Oc9P1khwCfdrrz
    dRK26ouewhZsBTU48srOrhU=
    =Nku0
    -----END PGP SIGNATURE-----


  2. [BUG] linux-next: Tree for May 19 - BUG at arch/x86/kernel/io_apic_64.c:353!

    Hi Stephen,

    The next-20080519 kernel panics at the add_pin_to_irq(), while booting up on one
    of the x86_64 machine.

    kernel BUG at arch/x86/kernel/io_apic_64.c:353!
    invalid opcode: 0000 [1] SMP
    last sysfs file:
    CPU 24
    Modules linked in:
    Pid: 1, comm: swapper Not tainted 2.6.26-rc3-next-20080519-sched-devel.git-autotest #1
    RIP: 0010:[] [] add_pin_to_irq+0x7a/0x90
    RSP: 0018:ffff81061e4cbb60 EFLAGS: 00010216
    RAX: 00000000000000f0 RBX: 00000000000000f0 RCX: 0000000000000001
    RDX: 0000000000000018 RSI: 0000000000000006 RDI: 00000000000000f0
    RBP: 0000000000000006 R08: 0000000000000018 R09: 0000000000000006
    R10: 0000000000000008 R11: ffffffff80391ca6 R12: 0000000000000001
    R13: 0000000000000001 R14: 0000000000000018 R15: ffff81061e4cbc04
    FS: 0000000000000000(0000) GS:ffff810bfe7bf540(0000) knlGS:0000000000000000
    CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Process swapper (pid: 1, threadinfo ffff81061e4ca000, task ffff81032e4b96d0)
    Stack: 0000000000000006 ffffffff8021cefe 00000000000000f0 0000000000000001
    0000000000000000 0000000000000000 ffff81061e4cbc00 ffffffff80219f91
    00000000000000f0 0000000000000000 0000000000000001 ffffffff8021a01a
    Call Trace:
    [] io_apic_set_pci_routing+0x7e/0xb0
    [] mp_register_gsi+0xb1/0xd0
    [] acpi_register_gsi+0x6a/0x70
    [] acpi_pci_irq_enable+0x14f/0x1f9
    [] acpi_pci_allocate_irq+0x0/0x4c
    [] do_pci_enable_device+0x4a/0x70
    [] __pci_enable_device_flags+0x51/0x60
    [] tg3_init_one+0x58/0x15e0
    [] default_wake_function+0x0/0x10
    [] set_cpus_allowed_ptr+0xc2/0xf0
    [] pci_device_probe+0xdf/0x130
    [] driver_probe_device+0x96/0x1a0
    [] __driver_attach+0x89/0x90
    [] __driver_attach+0x0/0x90
    [] bus_for_each_dev+0x4d/0x80
    [] kmem_cache_alloc+0xc8/0xf0
    [] bus_add_driver+0xae/0x220
    [] driver_register+0x56/0x130
    [] __pci_register_driver+0x68/0xb0
    [] tg3_init+0x0/0x20
    [] kernel_init+0x123/0x2f0
    [] child_rip+0xa/0x12
    [] kernel_init+0x0/0x2f0
    [] child_rip+0x0/0x12


    Code: 89 05 f7 53 41 00 7f 29 48 0f bf c1 48 8d 14 00 48 c1 e0 03 48 29 d0 48 8d 90 e0 f3 71 80 66 89 32 66 44 89 42 02 48 83 c4 08 c3 <0f> 0b eb fe 66 90 48 c7 c7 68 05 5c 80 31 c0 e8 d2 77 01 00 66
    RIP [] add_pin_to_irq+0x7a/0x90
    RSP
    ---[ end trace 13dd5b9e45b9159b ]---
    Kernel panic - not syncing: Attempted to kill init!
    Pid: 1, comm: swapper Tainted: G D 2.6.26-rc3-next-20080519-sched-devel.git-autotest #1

    Call Trace:
    [] panic+0x86/0x170
    [] printk+0x4e/0x60
    [] do_exit+0x761/0x770
    [] oops_end+0xc1/0xd0
    [] do_invalid_op+0x86/0xa0
    [] add_pin_to_irq+0x7a/0x90
    [] vt_console_print+0x224/0x2f0
    [] dummycon_dummy+0x0/0x10
    [] error_exit+0x0/0x51
    [] acpi_pci_allocate_irq+0x0/0x4c
    [] add_pin_to_irq+0x7a/0x90
    [] io_apic_set_pci_routing+0x7e/0xb0
    [] mp_register_gsi+0xb1/0xd0
    [] acpi_register_gsi+0x6a/0x70
    [] acpi_pci_irq_enable+0x14f/0x1f9
    [] acpi_pci_allocate_irq+0x0/0x4c
    [] do_pci_enable_device+0x4a/0x70
    [] __pci_enable_device_flags+0x51/0x60
    [] tg3_init_one+0x58/0x15e0
    [] default_wake_function+0x0/0x10
    [] set_cpus_allowed_ptr+0xc2/0xf0
    [] pci_device_probe+0xdf/0x130
    [] driver_probe_device+0x96/0x1a0
    [] __driver_attach+0x89/0x90
    [] __driver_attach+0x0/0x90
    [] bus_for_each_dev+0x4d/0x80
    [] kmem_cache_alloc+0xc8/0xf0
    [] bus_add_driver+0xae/0x220
    [] driver_register+0x56/0x130
    [] __pci_register_driver+0x68/0xb0
    [] tg3_init+0x0/0x20
    [] kernel_init+0x123/0x2f0
    [] child_rip+0xa/0x12
    [] kernel_init+0x0/0x2f0
    [] child_rip+0x0/0x12


    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()

    Hi,

    The next-20080519 kernel build fails on the x86_64 machine, when compiled
    with the randconfig.

    LD .tmp_vmlinux1
    crypto/built-in.o: In function `cryptd_alloc_hash':
    /root/kernels/linux-2.6.26-rc3/crypto/cryptd.c:485: undefined reference to `crypto_ahash_type'
    make: *** [.tmp_vmlinux1] Error 1


    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.


  4. Re: [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()

    On Mon, 19 May 2008 22:38:06 +0530 Kamalesh Babulal wrote:

    > Hi,
    >
    > The next-20080519 kernel build fails on the x86_64 machine, when compiled
    > with the randconfig.
    >
    > LD .tmp_vmlinux1
    > crypto/built-in.o: In function `cryptd_alloc_hash':
    > /root/kernels/linux-2.6.26-rc3/crypto/cryptd.c:485: undefined reference to `crypto_ahash_type'
    > make: *** [.tmp_vmlinux1] Error 1


    Fixed on Thu May 15: http://lkml.org/lkml/2008/5/15/433
    and Herbert says that he merged it on Fri May 16,
    so why did it miss being in linux-next on Mon May 19?

    Wrong tree/branch/whatever?

    ---
    ~Randy
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: linux-next: Tree for May 19

    Am Montag, den 19.05.2008, 17:41 +1000 schrieb Stephen Rothwell:
    > News:
    > I will stop making full tar balls tomorrow unless someone screams.
    > The LATEST file now contains the name of the version that the
    > patches are based on i.e. today, LATEST-IS-next-20080519 contains "v2.6.26-rc3".
    >
    > Changes since next-20080516:
    >
    > New tree: bkl-removal (this is Jonathan Corbet's tree)
    >
    > Removed trees: x86-fixes, sched-fixes (I don't know where they are
    > currently).
    >
    > Changed trees: x86 and sched are now the new auto merged trees.
    >


    Is it intentional that kernel.release is:

    $ cat include/config/kernel.release
    2.6.26-rc3-next-20080519-sched-devel.git

    all predecessors have had names like:
    2.6.26-rc2-next-20080516

    greetz




    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. Re: linux-next: Tree for May 19

    Hi Thomas,

    On Mon, 19 May 2008 20:42:00 +0200 Thomas Meyer wrote:
    >
    > Is it intentional that kernel.release is:
    >
    > $ cat include/config/kernel.release
    > 2.6.26-rc3-next-20080519-sched-devel.git
    >
    > all predecessors have had names like:
    > 2.6.26-rc2-next-20080516


    It was not intentional, I missed it sneaking in. It seems to be gone
    again today.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIMlE5TgG2atn1QN8RAtrKAJ0eozOwI60iRtYIGMcm6k z9ptBjrwCeOHK9
    NRPBTe0eATOS4G+GVQa3/zI=
    =rfqt
    -----END PGP SIGNATURE-----


  7. Re: [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()

    Randy Dunlap wrote:
    >
    > Fixed on Thu May 15: http://lkml.org/lkml/2008/5/15/433
    > and Herbert says that he merged it on Fri May 16,
    > so why did it miss being in linux-next on Mon May 19?
    >
    > Wrong tree/branch/whatever?


    Sorry, I forgot to push It's there now so should show up tomorrow.

    Cheers,
    --
    Visit Openswan at http://www.openswan.org/
    Email: Herbert Xu ~{PmV>HI~}
    Home Page: http://gondor.apana.org.au/~herbert/
    PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  8. [BUG] linux-next: Tree for May 19/20/21 - BUG at arch/x86/kernel/io_apic_64.c:353!

    Kamalesh Babulal wrote:
    > Hi Stephen,
    >
    > The next-20080519 kernel panics at the add_pin_to_irq(), while booting up on one
    > of the x86_64 machine.
    >
    > kernel BUG at arch/x86/kernel/io_apic_64.c:353!
    > invalid opcode: 0000 [1] SMP
    > last sysfs file:
    > CPU 24
    > Modules linked in:
    > Pid: 1, comm: swapper Not tainted 2.6.26-rc3-next-20080519-sched-devel.git-autotest #1
    > RIP: 0010:[] [] add_pin_to_irq+0x7a/0x90
    > RSP: 0018:ffff81061e4cbb60 EFLAGS: 00010216
    > RAX: 00000000000000f0 RBX: 00000000000000f0 RCX: 0000000000000001
    > RDX: 0000000000000018 RSI: 0000000000000006 RDI: 00000000000000f0
    > RBP: 0000000000000006 R08: 0000000000000018 R09: 0000000000000006
    > R10: 0000000000000008 R11: ffffffff80391ca6 R12: 0000000000000001
    > R13: 0000000000000001 R14: 0000000000000018 R15: ffff81061e4cbc04
    > FS: 0000000000000000(0000) GS:ffff810bfe7bf540(0000) knlGS:0000000000000000
    > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    > CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
    > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    > Process swapper (pid: 1, threadinfo ffff81061e4ca000, task ffff81032e4b96d0)
    > Stack: 0000000000000006 ffffffff8021cefe 00000000000000f0 0000000000000001
    > 0000000000000000 0000000000000000 ffff81061e4cbc00 ffffffff80219f91
    > 00000000000000f0 0000000000000000 0000000000000001 ffffffff8021a01a
    > Call Trace:
    > [] io_apic_set_pci_routing+0x7e/0xb0
    > [] mp_register_gsi+0xb1/0xd0
    > [] acpi_register_gsi+0x6a/0x70
    > [] acpi_pci_irq_enable+0x14f/0x1f9
    > [] acpi_pci_allocate_irq+0x0/0x4c
    > [] do_pci_enable_device+0x4a/0x70
    > [] __pci_enable_device_flags+0x51/0x60
    > [] tg3_init_one+0x58/0x15e0
    > [] default_wake_function+0x0/0x10
    > [] set_cpus_allowed_ptr+0xc2/0xf0
    > [] pci_device_probe+0xdf/0x130
    > [] driver_probe_device+0x96/0x1a0
    > [] __driver_attach+0x89/0x90
    > [] __driver_attach+0x0/0x90
    > [] bus_for_each_dev+0x4d/0x80
    > [] kmem_cache_alloc+0xc8/0xf0
    > [] bus_add_driver+0xae/0x220
    > [] driver_register+0x56/0x130
    > [] __pci_register_driver+0x68/0xb0
    > [] tg3_init+0x0/0x20
    > [] kernel_init+0x123/0x2f0
    > [] child_rip+0xa/0x12
    > [] kernel_init+0x0/0x2f0
    > [] child_rip+0x0/0x12
    >
    >
    > Code: 89 05 f7 53 41 00 7f 29 48 0f bf c1 48 8d 14 00 48 c1 e0 03 48 29 d0 48 8d 90 e0 f3 71 80 66 89 32 66 44 89 42 02 48 83 c4 08 c3 <0f> 0b eb fe 66 90 48 c7 c7 68 05 5c 80 31 c0 e8 d2 77 01 00 66
    > RIP [] add_pin_to_irq+0x7a/0x90
    > RSP
    > ---[ end trace 13dd5b9e45b9159b ]---
    > Kernel panic - not syncing: Attempted to kill init!
    > Pid: 1, comm: swapper Tainted: G D 2.6.26-rc3-next-20080519-sched-devel.git-autotest #1
    >
    > Call Trace:
    > [] panic+0x86/0x170
    > [] printk+0x4e/0x60
    > [] do_exit+0x761/0x770
    > [] oops_end+0xc1/0xd0
    > [] do_invalid_op+0x86/0xa0
    > [] add_pin_to_irq+0x7a/0x90
    > [] vt_console_print+0x224/0x2f0
    > [] dummycon_dummy+0x0/0x10
    > [] error_exit+0x0/0x51
    > [] acpi_pci_allocate_irq+0x0/0x4c
    > [] add_pin_to_irq+0x7a/0x90
    > [] io_apic_set_pci_routing+0x7e/0xb0
    > [] mp_register_gsi+0xb1/0xd0
    > [] acpi_register_gsi+0x6a/0x70
    > [] acpi_pci_irq_enable+0x14f/0x1f9
    > [] acpi_pci_allocate_irq+0x0/0x4c
    > [] do_pci_enable_device+0x4a/0x70
    > [] __pci_enable_device_flags+0x51/0x60
    > [] tg3_init_one+0x58/0x15e0
    > [] default_wake_function+0x0/0x10
    > [] set_cpus_allowed_ptr+0xc2/0xf0
    > [] pci_device_probe+0xdf/0x130
    > [] driver_probe_device+0x96/0x1a0
    > [] __driver_attach+0x89/0x90
    > [] __driver_attach+0x0/0x90
    > [] bus_for_each_dev+0x4d/0x80
    > [] kmem_cache_alloc+0xc8/0xf0
    > [] bus_add_driver+0xae/0x220
    > [] driver_register+0x56/0x130
    > [] __pci_register_driver+0x68/0xb0
    > [] tg3_init+0x0/0x20
    > [] kernel_init+0x123/0x2f0
    > [] child_rip+0xa/0x12
    > [] kernel_init+0x0/0x2f0
    > [] child_rip+0x0/0x12
    >
    >

    Hi Stephen,

    This kernel panic while booting up is reproducible with the next-20080519,
    next-20080520 and next-20080521 kernels.

    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: [BUG] linux-next: Tree for May 19/20/21 - BUG at arch/x86/kernel/io_apic_64.c:353!

    Hi Kamalesh,

    On Wed, 21 May 2008 22:56:54 +0530 Kamalesh Babulal wrote:
    >
    > This kernel panic while booting up is reproducible with the next-20080519,
    > next-20080520 and next-20080521 kernels.


    Thanks for the reports.

    Can you include the config when you send these, please. If it a standard
    config then just say "defconfig" (or whatever) otherwise please attach
    the config you used.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFINLswTgG2atn1QN8RAnnLAJ4klNfKT9UXyGDzTHNIZi flmT46HQCgkUBu
    dZihCo7cfYZAqXixoB3EkRM=
    =N7MC
    -----END PGP SIGNATURE-----


  10. Re: [BUG] linux-next: Tree for May 19/20/21 - BUG at arch/x86/kernel/io_apic_64.c:353!

    Stephen Rothwell wrote:
    > Hi Kamalesh,
    >
    > On Wed, 21 May 2008 22:56:54 +0530 Kamalesh Babulal wrote:
    >> This kernel panic while booting up is reproducible with the next-20080519,
    >> next-20080520 and next-20080521 kernels.

    >
    > Thanks for the reports.
    >
    > Can you include the config when you send these, please. If it a standard
    > config then just say "defconfig" (or whatever) otherwise please attach
    > the config you used.
    >

    Sure, from next report will send across the .config file also. Please find
    the .config file attached, for the kernel bug discussed.


    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.


+ Reply to Thread