This message contains a list of some regressions introduced between 2.6.26 and
2.6.27, for which there are no fixes in the mainline I know of. If any of them
have been fixed already, please let me know.
If you know of any other unresolved regressions introduced between 2.6.26
and 2.6.27, please let me know either and I'll add them to the list.
Also, please let me know if any of the entries below are invalid.
Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.
Listed regressions statistics:
Date Total Pending Unresolved
----------------------------------------
2008-11-09 196 28 23
2008-11-02 195 34 28
2008-10-26 190 34 29
2008-10-04 181 41 33
2008-09-27 173 35 28
2008-09-21 169 45 36
2008-09-15 163 46 32
2008-09-12 163 51 38
2008-09-07 150 43 33
2008-08-30 135 48 36
2008-08-23 122 48 40
2008-08-16 103 47 37
2008-08-10 80 52 31
2008-08-02 47 31 20
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11983
Subject : iwlagn: wrong command queue 31, command id 0x0
Submitter : Matt Mackall <[email protected]>
Date : 2008-11-06 4:16 (4 days old)
References : http://marc.info/?l=linux-kernel&m=122598672815803&w=4
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703
Handled-By : reinette chatre <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11892
Subject : Battery information and status disappearing and wrong thermal status.
Submitter : Mark <[email protected]>
Date : 2008-10-29 15:33 (12 days old)
Handled-By : Alexey Starikovskiy <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11876
Subject : RCU hang on cpu re-hotplug with 2.6.27rc8
Submitter : Andi Kleen <[email protected]>
Date : 2008-10-06 23:28 (35 days old)
References : http://marc.info/?l=linux-kernel&m=122333610602399&w=2
Handled-By : Paul E. McKenney <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11843
Subject : usb hdd problems with 2.6.27.2
Submitter : Luciano Rocha <[email protected]>
Date : 2008-10-22 16:22 (19 days old)
References : http://marc.info/?l=linux-kernel&m=122469318102679&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11836
Subject : Scheduler on C2D CPU and latest 2.6.27 kernel
Submitter : Zdenek Kabelac <[email protected]>
Date : 2008-10-21 9:59 (20 days old)
References : http://marc.info/?l=linux-kernel&m=122458320502371&w=4
Handled-By : Chris Snook <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11830
Subject : disk statistics issue in 2.6.27
Submitter : Miquel van Smoorenburg <[email protected]>
Date : 2008-10-19 11:31 (22 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=427e59f09fdba387547106de7bab980b7fff77be
References : http://marc.info/?l=linux-kernel&m=122441671421326&w=4
Handled-By : Jens Axboe <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11820
Subject : 2.6.27: 0 MHz CPU and wrong system time on AMD Geode system
Submitter : Antipov Dmitry <[email protected]>
Date : 2008-10-15 6:39 (26 days old)
References : http://marc.info/?l=linux-kernel&m=122405421010969&w=4
Handled-By : Jordan Crouse <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11795
Subject : ks959-sir dongle no longer works under 2.6.27 (REGRESSION)
Submitter : Alex Villacis Lasso <[email protected]>
Date : 2008-10-20 10:49 (21 days old)
Handled-By : Samuel Ortiz <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11698
Subject : 2.6.27-rc7, freezes with > 1 s2ram cycle
Submitter : Soeren Sonnenburg <[email protected]>
Date : 2008-09-29 11:29 (42 days old)
References : http://marc.info/?l=linux-kernel&m=122268780926859&w=4
Handled-By : Rafael J. Wysocki <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11608
Subject : 2.6.27-rc6 BUG: unable to handle kernel paging request
Submitter : John Daiker <[email protected]>
Date : 2008-09-16 23:00 (55 days old)
References : http://marc.info/?l=linux-kernel&m=122160611517267&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11607
Subject : 2.6.27-rc6 Bug in tty_chars_in_buffer
Submitter : John Daiker <[email protected]>
Date : 2008-09-15 2:26 (56 days old)
References : http://marc.info/?l=linux-kernel&m=122144565514490&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11569
Subject : Panic stop CPUs regression
Submitter : Andi Kleen <[email protected]>
Date : 2008-09-02 13:49 (69 days old)
References : http://marc.info/?l=linux-kernel&m=122036356127282&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11543
Subject : kernel panic: softlockup in tick_periodic() ???
Submitter : Joshua Hoblitt <[email protected]>
Date : 2008-09-11 16:46 (60 days old)
References : http://marc.info/?l=linux-kernel&m=122117786124326&w=4
Handled-By : Thomas Gleixner <[email protected]>
Cyrill Gorcunov <[email protected]>
Ingo Molnar <[email protected]>
Cyrill Gorcunov <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11476
Subject : failure to associate after resume from suspend to ram
Submitter : Michael S. Tsirkin <[email protected]>
Date : 2008-09-01 13:33 (70 days old)
References : http://marc.info/?l=linux-kernel&m=122028529415108&w=4
Handled-By : Zhu Yi <[email protected]>
Dan Williams <[email protected]>
Jouni Malinen <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11407
Subject : suspend: unable to handle kernel paging request
Submitter : Vegard Nossum <[email protected]>
Date : 2008-08-21 17:28 (81 days old)
References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4
Handled-By : Rafael J. Wysocki <[email protected]>
Pekka Enberg <[email protected]>
Pavel Machek <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11404
Subject : BUG: in 2.6.23-rc3-git7 in do_cciss_intr
Submitter : rdunlap <[email protected]>
Date : 2008-08-21 5:52 (81 days old)
References : http://marc.info/?l=linux-kernel&m=121929819616273&w=4
http://marc.info/?l=linux-kernel&m=121932889105368&w=4
Handled-By : Miller, Mike (OS Dev) <[email protected]>
James Bottomley <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11380
Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
Submitter : Ingo Molnar <[email protected]>
Date : 2008-08-20 6:44 (82 days old)
References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11340
Subject : LTP overnight run resulted in unusable box
Submitter : Alexey Dobriyan <[email protected]>
Date : 2008-08-13 9:24 (89 days old)
References : http://marc.info/?l=linux-kernel&m=121861951902949&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11308
Subject : tbench regression on each kernel release from 2.6.22 -> 2.6.28
Submitter : Christoph Lameter <[email protected]>
Date : 2008-08-11 18:36 (91 days old)
References : http://marc.info/?l=linux-kernel&m=121847986119495&w=4
http://marc.info/?l=linux-kernel&m=122125737421332&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11264
Subject : Invalid op opcode in kernel/workqueue
Submitter : Jean-Luc Coulon <[email protected]>
Date : 2008-08-07 04:18 (95 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11215
Subject : INFO: possible recursive locking detected ps2_command
Submitter : Zdenek Kabelac <[email protected]>
Date : 2008-07-31 9:41 (102 days old)
References : http://marc.info/?l=linux-kernel&m=121749737011637&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11209
Subject : 2.6.27-rc1 process time accounting
Submitter : Lukas Hejtmanek <[email protected]>
Date : 2008-07-31 10:43 (102 days old)
References : http://marc.info/?l=linux-kernel&m=121750102917490&w=4
http://lkml.org/lkml/2008/9/30/199
http://marc.info/?l=linux-kernel&m=122470441624295&w=4
Handled-By : Peter Zijlstra <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11207
Subject : VolanoMark regression with 2.6.27-rc1
Submitter : Zhang, Yanmin <[email protected]>
Date : 2008-07-31 3:20 (102 days old)
References : http://marc.info/?l=linux-kernel&m=121747464114335&w=4
Handled-By : Zhang, Yanmin <[email protected]>
Peter Zijlstra <[email protected]>
Dhaval Giani <[email protected]>
Miao Xie <[email protected]>
Regressions with patches
------------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11865
Subject : WOL for E100 Doesn't Work Anymore
Submitter : roger <[email protected]>
Date : 2008-10-26 21:56 (15 days old)
Handled-By : Rafael J. Wysocki <[email protected]>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=18646&action=view
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 <[email protected]>
Date : 2008-10-19 11:26 (22 days old)
References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
Handled-By : Alan Stern <[email protected]>
Mike Isely <[email protected]>
Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11805
Subject : mounting XFS produces a segfault
Submitter : Tiago Maluta <[email protected]>
Date : 2008-10-21 18:00 (20 days old)
Handled-By : Dave Chinner <[email protected]>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=18397&action=view
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11664
Subject : acpi errors and random freeze on sony vaio sr
Submitter : Giovanni Pellerano <[email protected]>
Date : 2008-09-28 03:48 (43 days old)
Patch : http://marc.info/?l=linux-acpi&m=122514341319748&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11505
Subject : oltp ~10% regression with 2.6.27-rc5 on stoakley machine
Submitter : Lin Ming <[email protected]>
Date : 2008-09-04 7:06 (67 days old)
References : http://marc.info/?l=linux-kernel&m=122051202202373&w=4
http://marc.info/?t=122089704700005&r=1&w=4
Handled-By : Peter Zijlstra <[email protected]>
Gregory Haskins <[email protected]>
Ingo Molnar <[email protected]>
Patch : http://marc.info/?l=linux-kernel&m=122194673932703&w=4
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions introduced
between 2.6.26 and 2.6.27, unresolved as well as resolved, at:
http://bugzilla.kernel.org/show_bug.cgi?id=11167
Please let me know if there are any Bugzilla entries that should be added to
the list in there.
Thanks,
Rafael
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=11207
Subject : VolanoMark regression with 2.6.27-rc1
Submitter : Zhang, Yanmin <[email protected]>
Date : 2008-07-31 3:20 (102 days old)
References : http://marc.info/?l=linux-kernel&m=121747464114335&w=4
Handled-By : Zhang, Yanmin <[email protected]>
Peter Zijlstra <[email protected]>
Dhaval Giani <[email protected]>
Miao Xie <[email protected]>
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=11215
Subject : INFO: possible recursive locking detected ps2_command
Submitter : Zdenek Kabelac <[email protected]>
Date : 2008-07-31 9:41 (102 days old)
References : http://marc.info/?l=linux-kernel&m=121749737011637&w=4
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=11308
Subject : tbench regression on each kernel release from 2.6.22 -> 2.6.28
Submitter : Christoph Lameter <[email protected]>
Date : 2008-08-11 18:36 (91 days old)
References : http://marc.info/?l=linux-kernel&m=121847986119495&w=4
http://marc.info/?l=linux-kernel&m=122125737421332&w=4
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=11264
Subject : Invalid op opcode in kernel/workqueue
Submitter : Jean-Luc Coulon <[email protected]>
Date : 2008-08-07 04:18 (95 days old)
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=11209
Subject : 2.6.27-rc1 process time accounting
Submitter : Lukas Hejtmanek <[email protected]>
Date : 2008-07-31 10:43 (102 days old)
References : http://marc.info/?l=linux-kernel&m=121750102917490&w=4
http://lkml.org/lkml/2008/9/30/199
http://marc.info/?l=linux-kernel&m=122470441624295&w=4
Handled-By : Peter Zijlstra <[email protected]>
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=11340
Subject : LTP overnight run resulted in unusable box
Submitter : Alexey Dobriyan <[email protected]>
Date : 2008-08-13 9:24 (89 days old)
References : http://marc.info/?l=linux-kernel&m=121861951902949&w=4
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=11608
Subject : 2.6.27-rc6 BUG: unable to handle kernel paging request
Submitter : John Daiker <[email protected]>
Date : 2008-09-16 23:00 (55 days old)
References : http://marc.info/?l=linux-kernel&m=122160611517267&w=4
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=11569
Subject : Panic stop CPUs regression
Submitter : Andi Kleen <[email protected]>
Date : 2008-09-02 13:49 (69 days old)
References : http://marc.info/?l=linux-kernel&m=122036356127282&w=4
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=11476
Subject : failure to associate after resume from suspend to ram
Submitter : Michael S. Tsirkin <[email protected]>
Date : 2008-09-01 13:33 (70 days old)
References : http://marc.info/?l=linux-kernel&m=122028529415108&w=4
Handled-By : Zhu Yi <[email protected]>
Dan Williams <[email protected]>
Jouni Malinen <[email protected]>
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=11404
Subject : BUG: in 2.6.23-rc3-git7 in do_cciss_intr
Submitter : rdunlap <[email protected]>
Date : 2008-08-21 5:52 (81 days old)
References : http://marc.info/?l=linux-kernel&m=121929819616273&w=4
http://marc.info/?l=linux-kernel&m=121932889105368&w=4
Handled-By : Miller, Mike (OS Dev) <[email protected]>
James Bottomley <[email protected]>
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=11407
Subject : suspend: unable to handle kernel paging request
Submitter : Vegard Nossum <[email protected]>
Date : 2008-08-21 17:28 (81 days old)
References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4
Handled-By : Rafael J. Wysocki <[email protected]>
Pekka Enberg <[email protected]>
Pavel Machek <[email protected]>
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=11380
Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
Submitter : Ingo Molnar <[email protected]>
Date : 2008-08-20 6:44 (82 days old)
References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
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=11543
Subject : kernel panic: softlockup in tick_periodic() ???
Submitter : Joshua Hoblitt <[email protected]>
Date : 2008-09-11 16:46 (60 days old)
References : http://marc.info/?l=linux-kernel&m=122117786124326&w=4
Handled-By : Thomas Gleixner <[email protected]>
Cyrill Gorcunov <[email protected]>
Ingo Molnar <[email protected]>
Cyrill Gorcunov <[email protected]>
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=11505
Subject : oltp ~10% regression with 2.6.27-rc5 on stoakley machine
Submitter : Lin Ming <[email protected]>
Date : 2008-09-04 7:06 (67 days old)
References : http://marc.info/?l=linux-kernel&m=122051202202373&w=4
http://marc.info/?t=122089704700005&r=1&w=4
Handled-By : Peter Zijlstra <[email protected]>
Gregory Haskins <[email protected]>
Ingo Molnar <[email protected]>
Patch : http://marc.info/?l=linux-kernel&m=122194673932703&w=4
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=11664
Subject : acpi errors and random freeze on sony vaio sr
Submitter : Giovanni Pellerano <[email protected]>
Date : 2008-09-28 03:48 (43 days old)
Patch : <<a href="http://marc.info/?l=linux-acpi&m=122514341319748&w=4
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=11698
Subject : 2.6.27-rc7, freezes with > 1 s2ram cycle
Submitter : Soeren Sonnenburg <[email protected]>
Date : 2008-09-29 11:29 (42 days old)
References : http://marc.info/?l=linux-kernel&m=122268780926859&w=4
Handled-By : Rafael J. Wysocki <[email protected]>
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=11795
Subject : ks959-sir dongle no longer works under 2.6.27 (REGRESSION)
Submitter : Alex Villacis Lasso <[email protected]>
Date : 2008-10-20 10:49 (21 days old)
Handled-By : Samuel Ortiz <[email protected]>
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=11805
Subject : mounting XFS produces a segfault
Submitter : Tiago Maluta <[email protected]>
Date : 2008-10-21 18:00 (20 days old)
Handled-By : Dave Chinner <[email protected]>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=18397&action=view
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=11820
Subject : 2.6.27: 0 MHz CPU and wrong system time on AMD Geode system
Submitter : Antipov Dmitry <[email protected]>
Date : 2008-10-15 6:39 (26 days old)
References : http://marc.info/?l=linux-kernel&m=122405421010969&w=4
Handled-By : Jordan Crouse <[email protected]>
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 <[email protected]>
Date : 2008-10-19 11:26 (22 days old)
References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
Handled-By : Alan Stern <[email protected]>
Mike Isely <[email protected]>
Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4
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=11836
Subject : Scheduler on C2D CPU and latest 2.6.27 kernel
Submitter : Zdenek Kabelac <[email protected]>
Date : 2008-10-21 9:59 (20 days old)
References : http://marc.info/?l=linux-kernel&m=122458320502371&w=4
Handled-By : Chris Snook <[email protected]>
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=11830
Subject : disk statistics issue in 2.6.27
Submitter : Miquel van Smoorenburg <[email protected]>
Date : 2008-10-19 11:31 (22 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=427e59f09fdba387547106de7bab980b7fff77be
References : http://marc.info/?l=linux-kernel&m=122441671421326&w=4
Handled-By : Jens Axboe <[email protected]>
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=11843
Subject : usb hdd problems with 2.6.27.2
Submitter : Luciano Rocha <[email protected]>
Date : 2008-10-22 16:22 (19 days old)
References : http://marc.info/?l=linux-kernel&m=122469318102679&w=4
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=11876
Subject : RCU hang on cpu re-hotplug with 2.6.27rc8
Submitter : Andi Kleen <[email protected]>
Date : 2008-10-06 23:28 (35 days old)
References : http://marc.info/?l=linux-kernel&m=122333610602399&w=2
Handled-By : Paul E. McKenney <[email protected]>
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=11865
Subject : WOL for E100 Doesn't Work Anymore
Submitter : roger <[email protected]>
Date : 2008-10-26 21:56 (15 days old)
Handled-By : Rafael J. Wysocki <[email protected]>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=18646&action=view
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=11892
Subject : Battery information and status disappearing and wrong thermal status.
Submitter : Mark <[email protected]>
Date : 2008-10-29 15:33 (12 days old)
Handled-By : Alexey Starikovskiy <[email protected]>
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=11983
Subject : iwlagn: wrong command queue 31, command id 0x0
Submitter : Matt Mackall <[email protected]>
Date : 2008-11-06 4:16 (4 days old)
References : http://marc.info/?l=linux-kernel&m=122598672815803&w=4
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703
Handled-By : reinette chatre <[email protected]>
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).
Yes, it should still be listed.
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11404
> Subject : BUG: in 2.6.23-rc3-git7 in do_cciss_intr
> Submitter : rdunlap <[email protected]>
> Date : 2008-08-21 5:52 (81 days old)
> References : http://marc.info/?l=linux-kernel&m=121929819616273&w=4
> http://marc.info/?l=linux-kernel&m=121932889105368&w=4
> Handled-By : Miller, Mike (OS Dev) <[email protected]>
> James Bottomley <[email protected]>
--
~Randy
On Sun, 2008-11-09 at 20:43 +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).
The cause has been found - a bug in the dpt_i2o driver that was hidden
until 2.6.27.
I've submitted a patch for 2.6.28 which will be included in the next
-rc, at which point I will submit it for 2.6.27-stable as well.
Thanks
Mike.
On Monday, 10 of November 2008, Miquel van Smoorenburg wrote:
> On Sun, 2008-11-09 at 20:43 +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).
>
> The cause has been found - a bug in the dpt_i2o driver that was hidden
> until 2.6.27.
>
> I've submitted a patch for 2.6.28 which will be included in the next
> -rc, at which point I will submit it for 2.6.27-stable as well.
Thanks for the info.
Can you please put a pointer to the patch into the Bugzilla entry?
Rafael
On Mon, 2008-11-10 at 00:49 +0100, Miquel van Smoorenburg wrote:
> On Sun, 2008-11-09 at 20:43 +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).
>
> The cause has been found - a bug in the dpt_i2o driver that was hidden
> until 2.6.27.
>
> I've submitted a patch for 2.6.28 which will be included in the next
> -rc, at which point I will submit it for 2.6.27-stable as well.
Actually, that's not quite the way it works anymore. As long as the
patch is similar for both trees, the way it's done now is to tag stable
patches with cc: Stable Tree <[email protected]> so they have automatic
notifies to the stable tree.
I'm assuming this patch should be so tagged?
James
On Sun, 2008-11-09 at 18:13 -0600, James Bottomley wrote:
> On Mon, 2008-11-10 at 00:49 +0100, Miquel van Smoorenburg wrote:
> > On Sun, 2008-11-09 at 20:43 +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).
> >
> > The cause has been found - a bug in the dpt_i2o driver that was hidden
> > until 2.6.27.
> >
> > I've submitted a patch for 2.6.28 which will be included in the next
> > -rc, at which point I will submit it for 2.6.27-stable as well.
>
> Actually, that's not quite the way it works anymore. As long as the
> patch is similar for both trees, the way it's done now is to tag stable
> patches with cc: Stable Tree <[email protected]> so they have automatic
> notifies to the stable tree.
Oh OK, I did not know that. The patch applies indeed to .27 and .28 .
> I'm assuming this patch should be so tagged?
Yes, thank you.
Mike.
* Rafael J. Wysocki <[email protected]> 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=11380
> Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
> Submitter : Ingo Molnar <[email protected]>
> Date : 2008-08-20 6:44 (82 days old)
> References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
had a quick look again: i believe this one still triggers, and it's
caused by some interaction between input code and workqueue code. I
think it started triggering when Oleg's workqueue annotation patches
went upstream:
6af8bf3: workqueues: add comments to __create_workqueue_key()
8448502: workqueues: do CPU_UP_CANCELED if CPU_UP_PREPARE fails
8de6d30: workqueues: schedule_on_each_cpu() can use schedule_work_on()
ef1ca23: workqueues: queue_work() can use queue_work_on()
a67da70: workqueues: lockdep annotations for flush_work()
3da1c84: workqueues: make get_online_cpus() useable for work->func()
8616a89: workqueues: schedule_on_each_cpu: use flush_work()
db70089: workqueues: implement flush_work()
1a4d9b0: workqueues: insert_work: use "list_head *" instead of "int tail"
plus when the cpu_active_map changes went upstream:
e761b77: cpu hotplug, sched: Introduce cpu_active_map and redo sched domain ma
so it's possibly an old input layer locking problem that only got
exposed via current changes. It's not an input layer bug that got
introduced ~80 days ago, but possibly an input layer problem. Or a CPU
hotplug bug. Or a workqueue bug.
Ingo
On 11/10, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[email protected]> 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=11380
> > Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
> > Submitter : Ingo Molnar <[email protected]>
> > Date : 2008-08-20 6:44 (82 days old)
> > References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
>
> had a quick look again: i believe this one still triggers, and it's
> caused by some interaction between input code and workqueue code. I
> think it started triggering when Oleg's workqueue annotation patches
> went upstream:
>
> 6af8bf3: workqueues: add comments to __create_workqueue_key()
> 8448502: workqueues: do CPU_UP_CANCELED if CPU_UP_PREPARE fails
> 8de6d30: workqueues: schedule_on_each_cpu() can use schedule_work_on()
> ef1ca23: workqueues: queue_work() can use queue_work_on()
> a67da70: workqueues: lockdep annotations for flush_work()
> 3da1c84: workqueues: make get_online_cpus() useable for work->func()
> 8616a89: workqueues: schedule_on_each_cpu: use flush_work()
> db70089: workqueues: implement flush_work()
> 1a4d9b0: workqueues: insert_work: use "list_head *" instead of "int tail"
"make get_online_cpus() useable for work->func()" changed the locking.
destroy_workqueue() was changed to take cpu_maps_update_begin() instead
of get_online_cpus(). Other patches can't make any difference afaics.
Currently I don't understand why lockdep complains, will try to do
more grepping later.
Oleg.
[Rafael J. Wysocki - Sun, Nov 09, 2008 at 08:43:19PM +0100]
| 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=11543
| Subject : kernel panic: softlockup in tick_periodic() ???
| Submitter : Joshua Hoblitt <[email protected]>
| Date : 2008-09-11 16:46 (60 days old)
| References : http://marc.info/?l=linux-kernel&m=122117786124326&w=4
| Handled-By : Thomas Gleixner <[email protected]>
| Cyrill Gorcunov <[email protected]>
| Ingo Molnar <[email protected]>
| Cyrill Gorcunov <[email protected]>
|
|
Waiting for info from Joshua
- Cyrill -
> On 11/10, Ingo Molnar wrote:
> >
> > * Rafael J. Wysocki <[email protected]> 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=11380
> > > Subject : lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16
> > > Submitter : Ingo Molnar <[email protected]>
> > > Date : 2008-08-20 6:44 (82 days old)
> > > References : http://marc.info/?l=linux-kernel&m=121921480931970&w=4
> >
> > had a quick look again: i believe this one still triggers, and it's
> > caused by some interaction between input code and workqueue code. I
> > think it started triggering when Oleg's workqueue annotation patches
> > went upstream:
> >
> > 6af8bf3: workqueues: add comments to __create_workqueue_key()
> > 8448502: workqueues: do CPU_UP_CANCELED if CPU_UP_PREPARE fails
> > 8de6d30: workqueues: schedule_on_each_cpu() can use schedule_work_on()
> > ef1ca23: workqueues: queue_work() can use queue_work_on()
> > a67da70: workqueues: lockdep annotations for flush_work()
> > 3da1c84: workqueues: make get_online_cpus() useable for work->func()
> > 8616a89: workqueues: schedule_on_each_cpu: use flush_work()
> > db70089: workqueues: implement flush_work()
> > 1a4d9b0: workqueues: insert_work: use "list_head *" instead of "int tail"
>
> "make get_online_cpus() useable for work->func()" changed the locking.
> destroy_workqueue() was changed to take cpu_maps_update_begin() instead
> of get_online_cpus(). Other patches can't make any difference afaics.
>
> Currently I don't understand why lockdep complains, will try to do
> more grepping later.
I check original report.
Is this really cpu hotplug related warnings?
it seem simple ABBA lock, right?
-> #4 (&dev->mutex){--..}:
[<c0160f87>] validate_chain+0x831/0xaa2
[<c0161872>] __lock_acquire+0x67a/0x6e0
[<c0161933>] lock_acquire+0x5b/0x81
[<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
[<c0782d02>] input_register_handle+0x26/0x7a dev->mutex
[<c04a62c9>] kbd_connect+0x64/0x8d
[<c0782842>] input_attach_handler+0x38/0x6b
[<c0784216>] input_register_handler+0x74/0xc3 input_mutex
[<c0f54e4b>] kbd_init+0x66/0x91
[<c0f54f7b>] vty_init+0xce/0xd7
[<c0f54952>] tty_init+0x193/0x197
[<c010112a>] do_one_initcall+0x42/0x133
[<c0f2d5cb>] kernel_init+0x16e/0x1d5
[<c0117c03>] kernel_thread_helper+0x7/0x10
[<ffffffff>] 0xffffffff
-> #3 (input_mutex){--..}:
[<c0160f87>] validate_chain+0x831/0xaa2
[<c0161872>] __lock_acquire+0x67a/0x6e0
[<c0161933>] lock_acquire+0x5b/0x81
[<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
[<c0783fbe>] input_register_device+0xff/0x17f input_mutex
[<c048a889>] acpi_button_add+0x31e/0x429
[<c04889f4>] acpi_device_probe+0x43/0xde
[<c052c67f>] driver_probe_device+0xa5/0x120
[<c052c73c>] __driver_attach+0x42/0x64 dev->sem
[<c052be91>] bus_for_each_dev+0x43/0x65
[<c052c507>] driver_attach+0x19/0x1b
[<c052c251>] bus_add_driver+0x9e/0x1a1
[<c052c8de>] driver_register+0x76/0xd2
[<c0488dc3>] acpi_bus_register_driver+0x3f/0x41
[<c0f51bf2>] acpi_button_init+0x32/0x51
[<c010112a>] do_one_initcall+0x42/0x133
[<c0f2d201>] do_async_initcalls+0x1a/0x2a
[<c0150eec>] run_workqueue+0xc3/0x193
[<c015195d>] worker_thread+0xbb/0xc7
[<c0153e2a>] kthread+0x40/0x66
[<c0117c03>] kernel_thread_helper+0x7/0x10
[<ffffffff>] 0xffffffff
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 <[email protected]>
> Date : 2008-10-19 11:26 (22 days old)
> References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
> Handled-By : Alan Stern <[email protected]>
> Mike Isely <[email protected]>
> Patch : http://linuxtv.org/hg/~mcisely/pvrusb2/rev/0bb411d8d2e4
This has been fixed already in .27 and in mainline with a patch from
Alan.
thanks,
greg k-h
On 11/11, KOSAKI Motohiro wrote:
>
> it seem simple ABBA lock, right?
>
> -> #4 (&dev->mutex){--..}:
> [<c0160f87>] validate_chain+0x831/0xaa2
> [<c0161872>] __lock_acquire+0x67a/0x6e0
> [<c0161933>] lock_acquire+0x5b/0x81
> [<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
> [<c0782d02>] input_register_handle+0x26/0x7a dev->mutex
^^^^^^^^^^
> [<c04a62c9>] kbd_connect+0x64/0x8d
> [<c0782842>] input_attach_handler+0x38/0x6b
> [<c0784216>] input_register_handler+0x74/0xc3 input_mutex
> [<c0f54e4b>] kbd_init+0x66/0x91
> [<c0f54f7b>] vty_init+0xce/0xd7
> [<c0f54952>] tty_init+0x193/0x197
> [<c010112a>] do_one_initcall+0x42/0x133
> [<c0f2d5cb>] kernel_init+0x16e/0x1d5
> [<c0117c03>] kernel_thread_helper+0x7/0x10
> [<ffffffff>] 0xffffffff
>
> -> #3 (input_mutex){--..}:
> [<c0160f87>] validate_chain+0x831/0xaa2
> [<c0161872>] __lock_acquire+0x67a/0x6e0
> [<c0161933>] lock_acquire+0x5b/0x81
> [<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
> [<c0783fbe>] input_register_device+0xff/0x17f input_mutex
> [<c048a889>] acpi_button_add+0x31e/0x429
> [<c04889f4>] acpi_device_probe+0x43/0xde
> [<c052c67f>] driver_probe_device+0xa5/0x120
> [<c052c73c>] __driver_attach+0x42/0x64 dev->sem
^^^^^^^^
input_dev->mutex != device->sem
> ...
> [<c0f2d201>] do_async_initcalls+0x1a/0x2a
> [<c0150eec>] run_workqueue+0xc3/0x193
> [<c015195d>] worker_thread+0xbb/0xc7
> [<c0153e2a>] kthread+0x40/0x66
What is the kernel version, btw? I can't find do_async_initcalls
in 2.6.27 or 2.6.28.
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.
Oleg.
* Oleg Nesterov <[email protected]> wrote:
> On 11/11, KOSAKI Motohiro wrote:
> >
> > it seem simple ABBA lock, right?
> >
> > -> #4 (&dev->mutex){--..}:
> > [<c0160f87>] validate_chain+0x831/0xaa2
> > [<c0161872>] __lock_acquire+0x67a/0x6e0
> > [<c0161933>] lock_acquire+0x5b/0x81
> > [<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
> > [<c0782d02>] input_register_handle+0x26/0x7a dev->mutex
> ^^^^^^^^^^
> > [<c04a62c9>] kbd_connect+0x64/0x8d
> > [<c0782842>] input_attach_handler+0x38/0x6b
> > [<c0784216>] input_register_handler+0x74/0xc3 input_mutex
> > [<c0f54e4b>] kbd_init+0x66/0x91
> > [<c0f54f7b>] vty_init+0xce/0xd7
> > [<c0f54952>] tty_init+0x193/0x197
> > [<c010112a>] do_one_initcall+0x42/0x133
> > [<c0f2d5cb>] kernel_init+0x16e/0x1d5
> > [<c0117c03>] kernel_thread_helper+0x7/0x10
> > [<ffffffff>] 0xffffffff
> >
> > -> #3 (input_mutex){--..}:
> > [<c0160f87>] validate_chain+0x831/0xaa2
> > [<c0161872>] __lock_acquire+0x67a/0x6e0
> > [<c0161933>] lock_acquire+0x5b/0x81
> > [<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
> > [<c0783fbe>] input_register_device+0xff/0x17f input_mutex
> > [<c048a889>] acpi_button_add+0x31e/0x429
> > [<c04889f4>] acpi_device_probe+0x43/0xde
> > [<c052c67f>] driver_probe_device+0xa5/0x120
> > [<c052c73c>] __driver_attach+0x42/0x64 dev->sem
> ^^^^^^^^
> input_dev->mutex != device->sem
>
> > ...
> > [<c0f2d201>] do_async_initcalls+0x1a/0x2a
> > [<c0150eec>] run_workqueue+0xc3/0x193
> > [<c015195d>] worker_thread+0xbb/0xc7
> > [<c0153e2a>] 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
On Tuesday, 11 of November 2008, Ingo Molnar wrote:
>
> * Oleg Nesterov <[email protected]> wrote:
>
> > On 11/11, KOSAKI Motohiro wrote:
> > >
> > > it seem simple ABBA lock, right?
> > >
> > > -> #4 (&dev->mutex){--..}:
> > > [<c0160f87>] validate_chain+0x831/0xaa2
> > > [<c0161872>] __lock_acquire+0x67a/0x6e0
> > > [<c0161933>] lock_acquire+0x5b/0x81
> > > [<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
> > > [<c0782d02>] input_register_handle+0x26/0x7a dev->mutex
> > ^^^^^^^^^^
> > > [<c04a62c9>] kbd_connect+0x64/0x8d
> > > [<c0782842>] input_attach_handler+0x38/0x6b
> > > [<c0784216>] input_register_handler+0x74/0xc3 input_mutex
> > > [<c0f54e4b>] kbd_init+0x66/0x91
> > > [<c0f54f7b>] vty_init+0xce/0xd7
> > > [<c0f54952>] tty_init+0x193/0x197
> > > [<c010112a>] do_one_initcall+0x42/0x133
> > > [<c0f2d5cb>] kernel_init+0x16e/0x1d5
> > > [<c0117c03>] kernel_thread_helper+0x7/0x10
> > > [<ffffffff>] 0xffffffff
> > >
> > > -> #3 (input_mutex){--..}:
> > > [<c0160f87>] validate_chain+0x831/0xaa2
> > > [<c0161872>] __lock_acquire+0x67a/0x6e0
> > > [<c0161933>] lock_acquire+0x5b/0x81
> > > [<c0a660e4>] mutex_lock_interruptible_nested+0xde/0x2f8
> > > [<c0783fbe>] input_register_device+0xff/0x17f input_mutex
> > > [<c048a889>] acpi_button_add+0x31e/0x429
> > > [<c04889f4>] acpi_device_probe+0x43/0xde
> > > [<c052c67f>] driver_probe_device+0xa5/0x120
> > > [<c052c73c>] __driver_attach+0x42/0x64 dev->sem
> > ^^^^^^^^
> > input_dev->mutex != device->sem
> >
> > > ...
> > > [<c0f2d201>] do_async_initcalls+0x1a/0x2a
> > > [<c0150eec>] run_workqueue+0xc3/0x193
> > > [<c015195d>] worker_thread+0xbb/0xc7
> > > [<c0153e2a>] 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
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 <[email protected]>
> > Date : 2008-10-19 11:26 (22 days old)
> > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
> > Handled-By : Alan Stern <[email protected]>
> > Mike Isely <[email protected]>
> > 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
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 <[email protected]>
> > > Date : 2008-10-19 11:26 (22 days old)
> > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
> > > Handled-By : Alan Stern <[email protected]>
> > > Mike Isely <[email protected]>
> > > 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
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 <[email protected]>
> > > > Date : 2008-10-19 11:26 (22 days old)
> > > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
> > > > Handled-By : Alan Stern <[email protected]>
> > > > Mike Isely <[email protected]>
> > > > 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
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 <[email protected]>
> > > Date : 2008-10-19 11:26 (22 days old)
> > > References : http://marc.info/?l=linux-kernel&m=122441560120027&w=4
> > > Handled-By : Alan Stern <[email protected]>
> > > Mike Isely <[email protected]>
> > > 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