2.6.28-rc3-git6: Reported regressions 2.6.26 -> 2.6.27 - Kernel

This is a discussion on 2.6.28-rc3-git6: Reported regressions 2.6.26 -> 2.6.27 - Kernel ; * Oleg Nesterov wrote: > On 11/11, KOSAKI Motohiro wrote: > > > > it seem simple ABBA lock, right? > > > > -> #4 (&dev->mutex){--..}: > > [ ] validate_chain+0x831/0xaa2 > > [ ] __lock_acquire+0x67a/0x6e0 > > [ ...

+ Reply to Thread
Page 3 of 3 FirstFirst 1 2 3
Results 41 to 46 of 46

Thread: 2.6.28-rc3-git6: Reported regressions 2.6.26 -> 2.6.27

  1. Re: [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16


    * Oleg Nesterov wrote:

    > On 11/11, KOSAKI Motohiro wrote:
    > >
    > > it seem simple ABBA lock, right?
    > >
    > > -> #4 (&dev->mutex){--..}:
    > > [] validate_chain+0x831/0xaa2
    > > [] __lock_acquire+0x67a/0x6e0
    > > [] lock_acquire+0x5b/0x81
    > > [] mutex_lock_interruptible_nested+0xde/0x2f8
    > > [] input_register_handle+0x26/0x7a dev->mutex

    > ^^^^^^^^^^
    > > [] kbd_connect+0x64/0x8d
    > > [] input_attach_handler+0x38/0x6b
    > > [] input_register_handler+0x74/0xc3 input_mutex
    > > [] kbd_init+0x66/0x91
    > > [] vty_init+0xce/0xd7
    > > [] tty_init+0x193/0x197
    > > [] do_one_initcall+0x42/0x133
    > > [] kernel_init+0x16e/0x1d5
    > > [] kernel_thread_helper+0x7/0x10
    > > [] 0xffffffff
    > >
    > > -> #3 (input_mutex){--..}:
    > > [] validate_chain+0x831/0xaa2
    > > [] __lock_acquire+0x67a/0x6e0
    > > [] lock_acquire+0x5b/0x81
    > > [] mutex_lock_interruptible_nested+0xde/0x2f8
    > > [] input_register_device+0xff/0x17f input_mutex
    > > [] acpi_button_add+0x31e/0x429
    > > [] acpi_device_probe+0x43/0xde
    > > [] driver_probe_device+0xa5/0x120
    > > [] __driver_attach+0x42/0x64 dev->sem

    > ^^^^^^^^
    > input_dev->mutex != device->sem
    >
    > > ...
    > > [] do_async_initcalls+0x1a/0x2a
    > > [] run_workqueue+0xc3/0x193
    > > [] worker_thread+0xbb/0xc7
    > > [] kthread+0x40/0x66

    >
    > What is the kernel version, btw? I can't find do_async_initcalls
    > in 2.6.27 or 2.6.28.


    i suspect it's an older version of tip/master that still had async
    initcalls.

    > Anyway, this really looks like lockdep bug to me. Even if we really
    > have the circular dependency (will try to grep more) I can't
    > understand why lockdep claims that polldev_mutex depends on
    > cpu_add_remove_lock.


    ok, will re-report if i can trigger it again with latest kernels.
    Rafael, please close this bug as cannot-reproduce for now.

    Ingo
    --
    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/

  2. Re: [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16

    On Tuesday, 11 of November 2008, Ingo Molnar wrote:
    >
    > * Oleg Nesterov wrote:
    >
    > > On 11/11, KOSAKI Motohiro wrote:
    > > >
    > > > it seem simple ABBA lock, right?
    > > >
    > > > -> #4 (&dev->mutex){--..}:
    > > > [] validate_chain+0x831/0xaa2
    > > > [] __lock_acquire+0x67a/0x6e0
    > > > [] lock_acquire+0x5b/0x81
    > > > [] mutex_lock_interruptible_nested+0xde/0x2f8
    > > > [] input_register_handle+0x26/0x7a dev->mutex

    > > ^^^^^^^^^^
    > > > [] kbd_connect+0x64/0x8d
    > > > [] input_attach_handler+0x38/0x6b
    > > > [] input_register_handler+0x74/0xc3 input_mutex
    > > > [] kbd_init+0x66/0x91
    > > > [] vty_init+0xce/0xd7
    > > > [] tty_init+0x193/0x197
    > > > [] do_one_initcall+0x42/0x133
    > > > [] kernel_init+0x16e/0x1d5
    > > > [] kernel_thread_helper+0x7/0x10
    > > > [] 0xffffffff
    > > >
    > > > -> #3 (input_mutex){--..}:
    > > > [] validate_chain+0x831/0xaa2
    > > > [] __lock_acquire+0x67a/0x6e0
    > > > [] lock_acquire+0x5b/0x81
    > > > [] mutex_lock_interruptible_nested+0xde/0x2f8
    > > > [] input_register_device+0xff/0x17f input_mutex
    > > > [] acpi_button_add+0x31e/0x429
    > > > [] acpi_device_probe+0x43/0xde
    > > > [] driver_probe_device+0xa5/0x120
    > > > [] __driver_attach+0x42/0x64 dev->sem

    > > ^^^^^^^^
    > > input_dev->mutex != device->sem
    > >
    > > > ...
    > > > [] do_async_initcalls+0x1a/0x2a
    > > > [] run_workqueue+0xc3/0x193
    > > > [] worker_thread+0xbb/0xc7
    > > > [] kthread+0x40/0x66

    > >
    > > What is the kernel version, btw? I can't find do_async_initcalls
    > > in 2.6.27 or 2.6.28.

    >
    > i suspect it's an older version of tip/master that still had async
    > initcalls.
    >
    > > Anyway, this really looks like lockdep bug to me. Even if we really
    > > have the circular dependency (will try to grep more) I can't
    > > understand why lockdep claims that polldev_mutex depends on
    > > cpu_add_remove_lock.

    >
    > ok, will re-report if i can trigger it again with latest kernels.
    > Rafael, please close this bug as cannot-reproduce for now.


    Done.

    Thanks,
    Rafael
    --
    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. Re: [Bug #11829] Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)

    On Tuesday, 11 of November 2008, Greg KH wrote:
    > On Sun, Nov 09, 2008 at 08:43:22PM +0100, Rafael J. Wysocki wrote:
    > > This message has been generated automatically as a part of a report
    > > of regressions introduced between 2.6.26 and 2.6.27.
    > >
    > > The following bug entry is on the current list of known regressions
    > > introduced between 2.6.26 and 2.6.27. Please verify if it still should
    > > be listed and let me know (either way).
    > >
    > >
    > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11829
    > > Subject : Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)
    > > Submitter : Justin Piszcz
    > > Date : 2008-10-19 11:26 (22 days old)
    > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
    > > Handled-By : Alan Stern
    > > Mike Isely
    > > Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4

    >
    > This has been fixed already in .27 and in mainline with a patch from
    > Alan.


    OK, closed it.

    Do you remember which of the Alan's patches is that?

    Rafael
    --
    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/

  4. Re: [Bug #11829] Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)

    On Tue, 11 Nov 2008, Rafael J. Wysocki wrote:

    > On Tuesday, 11 of November 2008, Greg KH wrote:
    > > On Sun, Nov 09, 2008 at 08:43:22PM +0100, Rafael J. Wysocki wrote:
    > > > This message has been generated automatically as a part of a report
    > > > of regressions introduced between 2.6.26 and 2.6.27.
    > > >
    > > > The following bug entry is on the current list of known regressions
    > > > introduced between 2.6.26 and 2.6.27. Please verify if it still should
    > > > be listed and let me know (either way).
    > > >
    > > >
    > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11829
    > > > Subject : Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)
    > > > Submitter : Justin Piszcz
    > > > Date : 2008-10-19 11:26 (22 days old)
    > > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
    > > > Handled-By : Alan Stern
    > > > Mike Isely
    > > > Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4

    > >
    > > This has been fixed already in .27 and in mainline with a patch from
    > > Alan.

    >
    > OK, closed it.
    >
    > Do you remember which of the Alan's patches is that?


    It wasn't a patch from Alan. It was from me. The commit ID is
    c82732a42896364296599b0f73f01c5e3fd781ae

    -Mike


    --

    Mike Isely
    isely @ pobox (dot) com
    PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
    --
    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: [Bug #11829] Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)

    On Tuesday, 11 of November 2008, Mike Isely wrote:
    > On Tue, 11 Nov 2008, Rafael J. Wysocki wrote:
    >
    > > On Tuesday, 11 of November 2008, Greg KH wrote:
    > > > On Sun, Nov 09, 2008 at 08:43:22PM +0100, Rafael J. Wysocki wrote:
    > > > > This message has been generated automatically as a part of a report
    > > > > of regressions introduced between 2.6.26 and 2.6.27.
    > > > >
    > > > > The following bug entry is on the current list of known regressions
    > > > > introduced between 2.6.26 and 2.6.27. Please verify if it still should
    > > > > be listed and let me know (either way).
    > > > >
    > > > >
    > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11829
    > > > > Subject : Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)
    > > > > Submitter : Justin Piszcz
    > > > > Date : 2008-10-19 11:26 (22 days old)
    > > > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
    > > > > Handled-By : Alan Stern
    > > > > Mike Isely
    > > > > Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4
    > > >
    > > > This has been fixed already in .27 and in mainline with a patch from
    > > > Alan.

    > >
    > > OK, closed it.
    > >
    > > Do you remember which of the Alan's patches is that?

    >
    > It wasn't a patch from Alan. It was from me. The commit ID is
    > c82732a42896364296599b0f73f01c5e3fd781ae


    OK, thanks.

    I added the "Fixed by" information to the bug entry, for the record.

    Rafael
    --
    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: [Bug #11829] Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)

    On Tue, 11 Nov 2008, Rafael J. Wysocki wrote:

    > On Tuesday, 11 of November 2008, Greg KH wrote:
    > > On Sun, Nov 09, 2008 at 08:43:22PM +0100, Rafael J. Wysocki wrote:
    > > > This message has been generated automatically as a part of a report
    > > > of regressions introduced between 2.6.26 and 2.6.27.
    > > >
    > > > The following bug entry is on the current list of known regressions
    > > > introduced between 2.6.26 and 2.6.27. Please verify if it still should
    > > > be listed and let me know (either way).
    > > >
    > > >
    > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11829
    > > > Subject : Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)
    > > > Submitter : Justin Piszcz
    > > > Date : 2008-10-19 11:26 (22 days old)
    > > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
    > > > Handled-By : Alan Stern
    > > > Mike Isely
    > > > Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4

    > >
    > > This has been fixed already in .27 and in mainline with a patch from
    > > Alan.

    >
    > OK, closed it.
    >
    > Do you remember which of the Alan's patches is that?


    I wasn't one of mine. The patch was written by Mike Isely: commit
    c82732a42896364296599b0f73f01c5e3fd781ae.

    Alan Stern

    --
    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/

+ Reply to Thread
Page 3 of 3 FirstFirst 1 2 3