This message contains a list of some regressions introduced between 2.6.31 and
2.6.32, 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.31
and 2.6.32, 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
----------------------------------------
2010-01-10 130 44 40
2009-12-29 124 60 57
2009-11-21 86 29 25
2009-11-16 84 46 41
2009-10-26 66 42 37
2009-10-12 48 31 27
2009-10-02 22 15 9
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15042
Subject : socket(PF_INET6 hangs when ipv6 not yet initialized
Submitter : Marc Haber <[email protected]>
Date : 2010-01-10 14:28 (1 days old)
References : http://marc.info/?l=linux-kernel&m=126313553029280&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14970
Subject : IBM Trackpoint Device changed - Scrolling doesn't work
Submitter : Victor Hooi <[email protected]>
Date : 2010-01-01 21:53 (10 days old)
Handled-By : Dmitry Torokhov <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14943
Subject : nfs regression?
Submitter : Nikola Ciprich <[email protected]>
Date : 2009-12-28 12:10 (14 days old)
References : http://marc.info/?l=linux-kernel&m=126200276223524&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14939
Subject : drm: random hang with i915
Submitter : Arnd Bergmann <[email protected]>
Date : 2009-12-07 17:30 (35 days old)
References : http://marc.info/?l=linux-kernel&m=126020704125723&w=4
Handled-By : Jesse Barnes <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14933
Subject : OOM killer unexpectedly called
Submitter : A. Boulan <[email protected]>
Date : 2009-12-24 23:42 (18 days old)
References : http://marc.info/?l=linux-kernel&m=126169821317492&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14922
Subject : 2.6.32 seemed to have broken nVidia MCP7A sata controller
Submitter : Mike Cui <[email protected]>
Date : 2009-12-19 6:13 (23 days old)
References : http://marc.info/?l=linux-ide&m=126120323407742&w=4
Handled-By : Jeff Garzik <[email protected]>
Robert Hancock <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14903
Subject : Kernel panic - not syncing: Attempted to kill init!
Submitter : Zhiyong Wu <[email protected]>
Date : 2009-12-18 4:08 (24 days old)
References : http://marc.info/?l=linux-kernel&m=126110931124738&w=4
Handled-By : Américo Wang <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14898
Subject : ksoftirqd problem
Submitter : Nico <[email protected]>
Date : 2009-12-13 19:05 (29 days old)
References : http://marc.info/?l=linux-kernel&m=126073114325690&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14897
Subject : i915: Commit 0e442c60 causes flickering
Submitter : David John <[email protected]>
Date : 2009-12-09 17:26 (33 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c
References : http://marc.info/?l=linux-kernel&m=126037889600769&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14895
Subject : BUG in kernel 2.6.32 when using luks encrypted root and RAID0..
Submitter : r4 <[email protected]>
Date : 2009-12-03 18:24 (39 days old)
References : http://marc.info/?l=linux-kernel&m=125986664904751&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14894
Subject : pohmelfs: NULL pointer dereference
Submitter : Alexander Beregalov <[email protected]>
Date : 2009-12-02 1:11 (40 days old)
References : http://marc.info/?l=linux-kernel&m=125971633107940&w=4
Handled-By : Evgeniy Polyakov <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14892
Subject : intel, KMS, suspend2ram resume, screen black
Submitter : Norbert Preining <[email protected]>
Date : 2009-11-24 4:35 (48 days old)
References : http://marc.info/?l=linux-kernel&m=125903731125558&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14891
Subject : Deadlock regression related to NFS root
Submitter : Stephen R. van den Berg <[email protected]>
Date : 2009-11-24 0:24 (48 days old)
References : http://marc.info/?l=linux-kernel&m=125902279909452&w=4
Handled-By : Trond Myklebust <[email protected]>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14886
Subject : Asus P2B-DS not detected as SMP moterboard
Submitter : Lorenzo Buzzi <[email protected]>
Date : 2009-12-27 17:20 (15 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14868
Subject : flood of "don't try to register things with the same name in the same directory." on upgrade to 2.6.32
Submitter : Rich Ercolani <[email protected]>
Date : 2009-12-24 02:44 (18 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14841
Subject : unable to enumerate USB device on port X after suspend/resume
Submitter : Fruhwirth Clemens <[email protected]>
Date : 2009-12-19 11:45 (23 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14817
Subject : When is system under load, then freeze/HD fail
Submitter : okias <[email protected]>
Date : 2009-12-15 11:12 (27 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14783
Subject : Unhandled IRQ on Thinkpad R61i: "irq 16: nobody cared"
Submitter : Stefan Zegenhagen <[email protected]>
Date : 2009-12-10 19:14 (32 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14782
Subject : Suspend hangs Lenovo SL300 after gdm login
Submitter : Gary Trakhman <[email protected]>
Date : 2009-12-10 18:53 (32 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=03ba3782e8dcc5b0e1efe440d33084f066e38cae
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14748
Subject : e1000e NIC not working after reboot
Submitter : Maciek Sitarz <[email protected]>
Date : 2009-12-06 13:04 (36 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14747
Subject : bisected 2.6.32 regression: synaptics touchpad doesn't work
Submitter : François Valenduc <[email protected]>
Date : 2009-12-06 11:16 (36 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14742
Subject : 2.6.32 new menu idle governor causes very high CPU temp
Submitter : <[email protected]>
Date : 2009-12-05 17:24 (37 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14695
Subject : regression in karmic thermal control
Submitter : Bugie <[email protected]>
Date : 2009-11-26 08:45 (46 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14670
Subject : i915: playing video via XVideo extension makes the screen flicker
Submitter : Thomas Meyer <[email protected]>
Date : 2009-11-23 13:15 (49 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14667
Subject : bisected 2.6.32 EC regression - Temperatures not correctly detected after suspend - Dell Studio XPS 16 laptop
Submitter : Federico Chiacchiaretta <[email protected]>
Date : 2009-11-22 20:42 (50 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14657
Subject : perf subsystem breakage in 2.6.32-rc7
Submitter : Arjan van de Ven <[email protected]>
Date : 2009-11-19 19:50 (53 days old)
References : http://marc.info/?l=linux-kernel&m=125866013419738&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14656
Subject : Oops at __rmqueue+0x98 with 2.6.32-rc6
Submitter : Lucas C. Villa Real <[email protected]>
Date : 2009-11-19 3:48 (53 days old)
References : http://marc.info/?l=linux-kernel&m=125860255229092&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14625
Subject : Commit d451564 breaks ARM
Submitter : Russell King <[email protected]>
Date : 2009-11-13 15:11 (59 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d4515646699b6ad7b1a98ceb871296b957f3ef47
References : http://marc.info/?l=linux-kernel&m=125812520315835&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14624
Subject : ath9k: BUG kmalloc-8192: Poison overwritten
Submitter : Miles Lane <[email protected]>
Date : 2009-11-12 4:58 (60 days old)
References : http://marc.info/?l=linux-kernel&m=125800196520396&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14621
Subject : specjbb2005 and aim7 regression with 2.6.32-rc kernels
Submitter : Zhang, Yanmin <[email protected]>
Date : 2009-11-06 7:38 (66 days old)
References : http://marc.info/?l=linux-kernel&m=125749310413174&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14504
Subject : intermittent hibernation problem again
Submitter : Ferenc Wágner <[email protected]>
Date : 2009-10-28 23:49 (75 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
Submitter : Justin P. Mattock <[email protected]>
Date : 2009-10-23 16:45 (80 days old)
References : http://lkml.org/lkml/2009/10/23/252
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14482
Subject : kernel BUG at fs/dcache.c:670 +lvm +md +ext3
Submitter : Alexander Clouter <[email protected]>
Date : 2009-10-23 10:30 (80 days old)
References : http://lkml.org/lkml/2009/10/23/50
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14442
Subject : resume after hibernate: /dev/sdb drops and returns as /dev/sde
Submitter : Duncan <[email protected]>
Date : 2009-10-20 01:52 (83 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14426
Subject : CE: hpet increasing min_delta_ns flood
Submitter : Thibault Mondary <[email protected]>
Date : 2009-10-17 09:29 (86 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14417
Subject : [Regression] Wireless driver iwlagn+iwlcore doesn't work after resume (needs reloading)
Submitter : Eddy Petrișor <[email protected]>
Date : 2009-10-16 11:07 (87 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14406
Subject : uvcvideo stopped work on Toshiba
Submitter : okias <[email protected]>
Date : 2009-10-14 19:08 (89 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14376
Subject : Kernel NULL pointer dereference/ kvm subsystem
Submitter : Don Dupuis <[email protected]>
Date : 2009-10-06 14:38 (97 days old)
References : http://marc.info/?l=linux-kernel&m=125484025021737&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14298
Subject : warning at manage.c:361 (set_irq_wake), matrix-keypad related?
Submitter : Pavel Machek <[email protected]>
Date : 2009-09-30 20:07 (103 days old)
References : http://marc.info/?l=linux-kernel&m=125434130703538&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14297
Subject : console resume broken since ba15ab0e8d
Submitter : Sascha Hauer <[email protected]>
Date : 2009-09-30 15:11 (103 days old)
References : http://marc.info/?l=linux-kernel&m=125432349404060&w=4
Regressions with patches
------------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15040
Subject : High cpu temperature with 2.6.32
Submitter : Dimitrios Apostolou <[email protected]>
Date : 2010-01-06 17:39 (5 days old)
References : http://marc.info/?l=linux-kernel&m=126279952723036&w=4
Handled-By : Arjan van de Ven <[email protected]>
Patch : http://patchwork.kernel.org/patch/71962/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14896
Subject : REGRESSION for RT2561/RT61 in 2.6.32, related to power saving
Submitter : Alan Stern <[email protected]>
Date : 2009-12-06 22:12 (36 days old)
References : http://marc.info/?l=linux-kernel&m=126013756829691&w=4
Handled-By : Gertjan van Wingerde <[email protected]>
Patch : http://patchwork.kernel.org/patch/67338/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14889
Subject : System wakeup by time not working anymore
Submitter : Malte Schröder <[email protected]>
Date : 2009-12-03 18:06 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=abd6633c67925f90775bb74755f9c547e30f1f20
References : http://marc.info/?l=linux-kernel&m=125986362631900&w=4
Handled-By : OGAWA Hirofumi <[email protected]>
Patch : http://patchwork.kernel.org/patch/70212/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14483
Subject : Interrupts enabled after irqrouter_resume - iMac9,1
Submitter : Justin Mattock <[email protected]>
Date : 2009-10-25 19:58 (78 days old)
References : http://marc.info/?l=linux-kernel&m=125650070420168&w=4
Handled-By : Xiaotian Feng <[email protected]>
Patch : http://patchwork.kernel.org/patch/64771/
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.31 and 2.6.32, unresolved as well as resolved, at:
http://bugzilla.kernel.org/show_bug.cgi?id=14230
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.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14297
Subject : console resume broken since ba15ab0e8d
Submitter : Sascha Hauer <[email protected]>
Date : 2009-09-30 15:11 (103 days old)
References : http://marc.info/?l=linux-kernel&m=125432349404060&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14298
Subject : warning at manage.c:361 (set_irq_wake), matrix-keypad related?
Submitter : Pavel Machek <[email protected]>
Date : 2009-09-30 20:07 (103 days old)
References : http://marc.info/?l=linux-kernel&m=125434130703538&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14426
Subject : CE: hpet increasing min_delta_ns flood
Submitter : Thibault Mondary <[email protected]>
Date : 2009-10-17 09:29 (86 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14417
Subject : [Regression] Wireless driver iwlagn+iwlcore doesn't work after resume (needs reloading)
Submitter : Eddy Petrișor <[email protected]>
Date : 2009-10-16 11:07 (87 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14442
Subject : resume after hibernate: /dev/sdb drops and returns as /dev/sde
Submitter : Duncan <[email protected]>
Date : 2009-10-20 01:52 (83 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14621
Subject : specjbb2005 and aim7 regression with 2.6.32-rc kernels
Submitter : Zhang, Yanmin <[email protected]>
Date : 2009-11-06 7:38 (66 days old)
References : http://marc.info/?l=linux-kernel&m=125749310413174&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14625
Subject : Commit d451564 breaks ARM
Submitter : Russell King <[email protected]>
Date : 2009-11-13 15:11 (59 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d4515646699b6ad7b1a98ceb871296b957f3ef47
References : http://marc.info/?l=linux-kernel&m=125812520315835&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14482
Subject : kernel BUG at fs/dcache.c:670 +lvm +md +ext3
Submitter : Alexander Clouter <[email protected]>
Date : 2009-10-23 10:30 (80 days old)
References : http://lkml.org/lkml/2009/10/23/50
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14895
Subject : BUG in kernel 2.6.32 when using luks encrypted root and RAID0..
Submitter : r4 <[email protected]>
Date : 2009-12-03 18:24 (39 days old)
References : http://marc.info/?l=linux-kernel&m=125986664904751&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14783
Subject : Unhandled IRQ on Thinkpad R61i: "irq 16: nobody cared"
Submitter : Stefan Zegenhagen <[email protected]>
Date : 2009-12-10 19:14 (32 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14667
Subject : bisected 2.6.32 EC regression - Temperatures not correctly detected after suspend - Dell Studio XPS 16 laptop
Submitter : Federico Chiacchiaretta <[email protected]>
Date : 2009-11-22 20:42 (50 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14817
Subject : When is system under load, then freeze/HD fail
Submitter : okias <[email protected]>
Date : 2009-12-15 11:12 (27 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14782
Subject : Suspend hangs Lenovo SL300 after gdm login
Submitter : Gary Trakhman <[email protected]>
Date : 2009-12-10 18:53 (32 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=03ba3782e8dcc5b0e1efe440d33084f066e38cae
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14903
Subject : Kernel panic - not syncing: Attempted to kill init!
Submitter : Zhiyong Wu <[email protected]>
Date : 2009-12-18 4:08 (24 days old)
References : http://marc.info/?l=linux-kernel&m=126110931124738&w=4
Handled-By : Américo Wang <[email protected]>
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14943
Subject : nfs regression?
Submitter : Nikola Ciprich <[email protected]>
Date : 2009-12-28 12:10 (14 days old)
References : http://marc.info/?l=linux-kernel&m=126200276223524&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14970
Subject : IBM Trackpoint Device changed - Scrolling doesn't work
Submitter : Victor Hooi <[email protected]>
Date : 2010-01-01 21:53 (10 days old)
Handled-By : Dmitry Torokhov <[email protected]>
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14939
Subject : drm: random hang with i915
Submitter : Arnd Bergmann <[email protected]>
Date : 2009-12-07 17:30 (35 days old)
References : http://marc.info/?l=linux-kernel&m=126020704125723&w=4
Handled-By : Jesse Barnes <[email protected]>
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15042
Subject : socket(PF_INET6 hangs when ipv6 not yet initialized
Submitter : Marc Haber <[email protected]>
Date : 2010-01-10 14:28 (1 days old)
References : http://marc.info/?l=linux-kernel&m=126313553029280&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15040
Subject : High cpu temperature with 2.6.32
Submitter : Dimitrios Apostolou <[email protected]>
Date : 2010-01-06 17:39 (5 days old)
References : http://marc.info/?l=linux-kernel&m=126279952723036&w=4
Handled-By : Arjan van de Ven <[email protected]>
Patch : http://patchwork.kernel.org/patch/71962/
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14896
Subject : REGRESSION for RT2561/RT61 in 2.6.32, related to power saving
Submitter : Alan Stern <[email protected]>
Date : 2009-12-06 22:12 (36 days old)
References : http://marc.info/?l=linux-kernel&m=126013756829691&w=4
Handled-By : Gertjan van Wingerde <[email protected]>
Patch : http://patchwork.kernel.org/patch/67338/
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14898
Subject : ksoftirqd problem
Submitter : Nico <[email protected]>
Date : 2009-12-13 19:05 (29 days old)
References : http://marc.info/?l=linux-kernel&m=126073114325690&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14922
Subject : 2.6.32 seemed to have broken nVidia MCP7A sata controller
Submitter : Mike Cui <[email protected]>
Date : 2009-12-19 6:13 (23 days old)
References : http://marc.info/?l=linux-ide&m=126120323407742&w=4
Handled-By : Jeff Garzik <[email protected]>
Robert Hancock <[email protected]>
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14933
Subject : OOM killer unexpectedly called
Submitter : A. Boulan <[email protected]>
Date : 2009-12-24 23:42 (18 days old)
References : http://marc.info/?l=linux-kernel&m=126169821317492&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14886
Subject : Asus P2B-DS not detected as SMP moterboard
Submitter : Lorenzo Buzzi <[email protected]>
Date : 2009-12-27 17:20 (15 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14897
Subject : i915: Commit 0e442c60 causes flickering
Submitter : David John <[email protected]>
Date : 2009-12-09 17:26 (33 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c
References : http://marc.info/?l=linux-kernel&m=126037889600769&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14891
Subject : Deadlock regression related to NFS root
Submitter : Stephen R. van den Berg <[email protected]>
Date : 2009-11-24 0:24 (48 days old)
References : http://marc.info/?l=linux-kernel&m=125902279909452&w=4
Handled-By : Trond Myklebust <[email protected]>
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14894
Subject : pohmelfs: NULL pointer dereference
Submitter : Alexander Beregalov <[email protected]>
Date : 2009-12-02 1:11 (40 days old)
References : http://marc.info/?l=linux-kernel&m=125971633107940&w=4
Handled-By : Evgeniy Polyakov <[email protected]>
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14742
Subject : 2.6.32 new menu idle governor causes very high CPU temp
Submitter : <[email protected]>
Date : 2009-12-05 17:24 (37 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14841
Subject : unable to enumerate USB device on port X after suspend/resume
Submitter : Fruhwirth Clemens <[email protected]>
Date : 2009-12-19 11:45 (23 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14892
Subject : intel, KMS, suspend2ram resume, screen black
Submitter : Norbert Preining <[email protected]>
Date : 2009-11-24 4:35 (48 days old)
References : http://marc.info/?l=linux-kernel&m=125903731125558&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14868
Subject : flood of "don't try to register things with the same name in the same directory." on upgrade to 2.6.32
Submitter : Rich Ercolani <[email protected]>
Date : 2009-12-24 02:44 (18 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14889
Subject : System wakeup by time not working anymore
Submitter : Malte Schröder <[email protected]>
Date : 2009-12-03 18:06 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=abd6633c67925f90775bb74755f9c547e30f1f20
References : http://marc.info/?l=linux-kernel&m=125986362631900&w=4
Handled-By : OGAWA Hirofumi <[email protected]>
Patch : http://patchwork.kernel.org/patch/70212/
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14747
Subject : bisected 2.6.32 regression: synaptics touchpad doesn't work
Submitter : François Valenduc <[email protected]>
Date : 2009-12-06 11:16 (36 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14748
Subject : e1000e NIC not working after reboot
Submitter : Maciek Sitarz <[email protected]>
Date : 2009-12-06 13:04 (36 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14695
Subject : regression in karmic thermal control
Submitter : Bugie <[email protected]>
Date : 2009-11-26 08:45 (46 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14670
Subject : i915: playing video via XVideo extension makes the screen flicker
Submitter : Thomas Meyer <[email protected]>
Date : 2009-11-23 13:15 (49 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
Submitter : Justin P. Mattock <[email protected]>
Date : 2009-10-23 16:45 (80 days old)
References : http://lkml.org/lkml/2009/10/23/252
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14624
Subject : ath9k: BUG kmalloc-8192: Poison overwritten
Submitter : Miles Lane <[email protected]>
Date : 2009-11-12 4:58 (60 days old)
References : http://marc.info/?l=linux-kernel&m=125800196520396&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14656
Subject : Oops at __rmqueue+0x98 with 2.6.32-rc6
Submitter : Lucas C. Villa Real <[email protected]>
Date : 2009-11-19 3:48 (53 days old)
References : http://marc.info/?l=linux-kernel&m=125860255229092&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14504
Subject : intermittent hibernation problem again
Submitter : Ferenc Wágner <[email protected]>
Date : 2009-10-28 23:49 (75 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14483
Subject : Interrupts enabled after irqrouter_resume - iMac9,1
Submitter : Justin Mattock <[email protected]>
Date : 2009-10-25 19:58 (78 days old)
References : http://marc.info/?l=linux-kernel&m=125650070420168&w=4
Handled-By : Xiaotian Feng <[email protected]>
Patch : http://patchwork.kernel.org/patch/64771/
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14657
Subject : perf subsystem breakage in 2.6.32-rc7
Submitter : Arjan van de Ven <[email protected]>
Date : 2009-11-19 19:50 (53 days old)
References : http://marc.info/?l=linux-kernel&m=125866013419738&w=4
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14406
Subject : uvcvideo stopped work on Toshiba
Submitter : okias <[email protected]>
Date : 2009-10-14 19:08 (89 days old)
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between 2.6.31 and 2.6.32. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14376
Subject : Kernel NULL pointer dereference/ kvm subsystem
Submitter : Don Dupuis <[email protected]>
Date : 2009-10-06 14:38 (97 days old)
References : http://marc.info/?l=linux-kernel&m=125484025021737&w=4
On Sun, Jan 10, 2010 at 4:56 PM, Rafael J. Wysocki <[email protected]> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. ?Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry ? ? ? : http://bugzilla.kernel.org/show_bug.cgi?id=14922
> Subject ? ? ? ? : 2.6.32 seemed to have broken nVidia MCP7A sata controller
> Submitter ? ? ? : Mike Cui <[email protected]>
> Date ? ? ? ? ? ?: 2009-12-19 6:13 (23 days old)
> References ? ? ?: http://marc.info/?l=linux-ide&m=126120323407742&w=4
> Handled-By ? ? ?: Jeff Garzik <[email protected]>
> ? ? ? ? ? ? ? ? ?Robert Hancock <[email protected]>
Still outstanding. Waiting for testing results from the reporter with
that drive on another AHCI controller, if possible. I CCed Peer Chen
from NVIDIA on the Bugzilla report, maybe they know if there is some
known problem with FPDMA AA on that controller.
On Sun, 10 Jan 2010 23:56:13 +0100 (CET)
"Rafael J. Wysocki" <[email protected]> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still
> should be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14657
> Subject : perf subsystem breakage in 2.6.32-rc7
> Submitter : Arjan van de Ven <[email protected]>
> Date : 2009-11-19 19:50 (53 days old)
> References :
> http://marc.info/?l=linux-kernel&m=125866013419738&w=4
patch available in the bugzilla, and also in
http://patchwork.kernel.org/patch/71962/
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
On Sun, Jan 10, 2010 at 11:56:17PM +0100, Rafael J. Wysocki ([email protected]) wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14894
> Subject : pohmelfs: NULL pointer dereference
> Submitter : Alexander Beregalov <[email protected]>
> Date : 2009-12-02 1:11 (40 days old)
> References : http://marc.info/?l=linux-kernel&m=125971633107940&w=4
> Handled-By : Evgeniy Polyakov <[email protected]>
There is a patch to fix the problem, I will test it in a day and push it
upstrem if it is ok.
--
Evgeniy Polyakov
On 01/11/2010 04:26 AM, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14897
> Subject : i915: Commit 0e442c60 causes flickering
> Submitter : David John <[email protected]>
> Date : 2009-12-09 17:26 (33 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c
> References : http://marc.info/?l=linux-kernel&m=126037889600769&w=4
>
>
>
Still present in 2.6.33-rc3.
Regards,
David.
On Sun, 2010-01-10 at 23:56 +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14621
> Subject : specjbb2005 and aim7 regression with 2.6.32-rc kernels
> Submitter : Zhang, Yanmin <[email protected]>
> Date : 2009-11-06 7:38 (66 days old)
> References : http://marc.info/?l=linux-kernel&m=125749310413174&w=4
FWIW, I couldn't reproduce the aim7 regression with my one little disk,
the opposite in fact, attributable to cfq low_latency switch.
(don't have specjbb2005, can't try to reproduce that one)
-Mike
2010/1/10 Rafael J. Wysocki <[email protected]>:
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14747
> Subject : bisected 2.6.32 regression: synaptics touchpad doesn't work
> Submitter : François Valenduc <[email protected]>
> Date : 2009-12-06 11:16 (36 days old)
Not sure if this is hackish or not, but some patch exists.
--
Rafał
On 01/10/10 14:56, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
> Subject : PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
> Submitter : Justin P. Mattock<[email protected]>
> Date : 2009-10-23 16:45 (80 days old)
> References : http://lkml.org/lkml/2009/10/23/252
>
>
>
I've played around with this. and
and much confused at what needs to happen.
(please feedback on what might be happening);
In any case I can have another try at finding a fix
so please leave open.
Justin P. Mattock
On Sun, 10 Jan 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14896
> Subject : REGRESSION for RT2561/RT61 in 2.6.32, related to power saving
> Submitter : Alan Stern <[email protected]>
> Date : 2009-12-06 22:12 (36 days old)
> References : http://marc.info/?l=linux-kernel&m=126013756829691&w=4
> Handled-By : Gertjan van Wingerde <[email protected]>
> Patch : http://patchwork.kernel.org/patch/67338/
This has been fixed by commit 93b6bd26b74efe46b4579592560f9f1cb7b61994.
Alan Stern
On Sun, 10 Jan 2010, Rafael J. Wysocki wrote:
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14841
> Subject : unable to enumerate USB device on port X after suspend/resume
> Submitter : Fruhwirth Clemens <[email protected]>
> Date : 2009-12-19 11:45 (23 days old)
This bug has been resolved as WILL NOT FIX. It ended up having nothing
to do with suspend or resume, it was caused by strange behavior in the
device hardware.
Alan Stern
Am Sonntag, 10. Januar 2010 23:56:10 schrieb Rafael J. Wysocki:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14406
> Subject : uvcvideo stopped work on Toshiba
> Submitter : okias <[email protected]>
> Date : 2009-10-14 19:08 (89 days old)
Have you tested with a kernel that has the attached patch?
If it doesn't help, the problem will have to be bisected.
Regards
Oliver
On Mon, Jan 11, 2010 at 4:15 PM, Alan Stern <[email protected]> wrote:
> On Sun, 10 Jan 2010, Rafael J. Wysocki wrote:
>
>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14841
>> Subject : unable to enumerate USB device on port X after suspend/resume
>> Submitter : Fruhwirth Clemens <[email protected]>
>> Date : 2009-12-19 11:45 (23 days old)
>
> This bug has been resolved as WILL NOT FIX. It ended up having nothing
> to do with suspend or resume, it was caused by strange behavior in the
> device hardware.
Should we track "automatic fallback to USB 1.1" as feature request?
You already said that this isn't easily possible with the way the USB
stack is structured at the moment (connect-centric-view instead of
port-centric-view). However, Windows does that fallback and I'm afraid
that this is the default device testing scenario.
--
Fruhwirth Clemens http://clemens.endorphin.org
Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
Yes, still should be listed.
Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189, that
contains
this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
The above commit removes the render reclock support, that ought to fix a common
kind of problem encountered on i915 hardware, but not on my machine.
Still need to boot with "nomodeset" to have a workable system.
On Mon, 11 Jan 2010 17:53:04 +0100
Thomas Meyer <[email protected]> wrote:
> Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still
> > should be listed and let me know (either way).
> >
>
> Yes, still should be listed.
>
> Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189, that
> contains
> this commit:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
>
> The above commit removes the render reclock support, that ought to
> fix a common kind of problem encountered on i915 hardware, but not on
> my machine.
>
> Still need to boot with "nomodeset" to have a workable system.
Does this patch prevent the flicker?
--
Jesse Barnes, Intel Open Source Technology Center
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 9187a17..0ab1bef 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -3806,7 +3806,7 @@ static void intel_increase_pllclock(struct drm_crtc *crtc, bool schedule)
if (IS_IRONLAKE(dev))
return;
- if (!dev_priv->lvds_downclock_avail)
+ if (!dev_priv->lvds_downclock_avail || 1)
return;
if (!HAS_PIPE_CXSR(dev) && (dpll & DISPLAY_RATE_SELECT_FPA1)) {
@@ -3845,7 +3845,7 @@ static void intel_decrease_pllclock(struct drm_crtc *crtc)
if (IS_IRONLAKE(dev))
return;
- if (!dev_priv->lvds_downclock_avail)
+ if (!dev_priv->lvds_downclock_avail || 1)
return;
/*
Am Montag, den 11.01.2010, 08:55 -0800 schrieb Jesse Barnes:
> On Mon, 11 Jan 2010 17:53:04 +0100
> Thomas Meyer <[email protected]> wrote:
>
> > Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.31 and 2.6.32.
> > >
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.31 and 2.6.32. Please verify if it still
> > > should be listed and let me know (either way).
> > >
> >
> > Yes, still should be listed.
> >
> > Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189, that
> > contains
> > this commit:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
> >
> > The above commit removes the render reclock support, that ought to
> > fix a common kind of problem encountered on i915 hardware, but not on
> > my machine.
> >
> > Still need to boot with "nomodeset" to have a workable system.
>
> Does this patch prevent the flicker?
No, sorry.
Reverting b42d4c5c6a872815d711e5d51a600f5122c38eee (i.e. the commit I
bisect my problem to) on top of 3c8ad49b015eb115fbd6982f56d530f53cf57f84
(i.e. 2.6.33-rc3-00147-g3c8ad49) make the problem go away.
My changes are:
diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
index f4b4aa2..15c6e6b 100644
--- a/drivers/gpu/drm/i915/intel_lvds.c
+++ b/drivers/gpu/drm/i915/intel_lvds.c
@@ -629,6 +629,8 @@ static enum drm_connector_status intel_lvds_detect(struct drm_connector *connect
{
enum drm_connector_status status = connector_status_connected;
+ return status;
+
if (!acpi_lid_open() && !dmi_check_system(bad_lid_status))
status = connector_status_disconnected;
On Mon, 11 Jan 2010 20:03:57 +0100
Thomas Meyer <[email protected]> wrote:
>
>
> Am 11.01.2010 um 17:55 schrieb Jesse Barnes
> <[email protected]>:
>
> > On Mon, 11 Jan 2010 17:53:04 +0100
> > Thomas Meyer <[email protected]> wrote:
> >
> >> Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki:
> >>> This message has been generated automatically as a part of a
> >>> report of regressions introduced between 2.6.31 and 2.6.32.
> >>>
> >>> The following bug entry is on the current list of known
> >>> regressions introduced between 2.6.31 and 2.6.32. Please verify
> >>> if it still should be listed and let me know (either way).
> >>>
> >>
> >> Yes, still should be listed.
> >>
> >> Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189,
> >> that contains
> >> this commit:
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
> >>
> >> The above commit removes the render reclock support, that ought to
> >> fix a common kind of problem encountered on i915 hardware, but not
> >> on my machine.
> >>
> >> Still need to boot with "nomodeset" to have a workable system.
> >
> > Does this patch prevent the flicker?
>
> By the way: how often and in what interval is the function
> intel_lvds_detect called?
>
> How long will/can the function acpi_lid_open take to complete?
> Maybe some acpi interpretation takes really long? Is this possible?
>
> Would this explain the flickering?
It should only be called when a client requests the connection status
(e.g. xrandr or the GNOME display applet).
The LVDS state will also be checked at ACPI LID event time, maybe your
platforms is getting spurious LID events?
If not, this bisection really confuses me...
--
Jesse Barnes, Intel Open Source Technology Center
On Monday 11 January 2010, Justin P. Mattock wrote:
> On 01/10/10 14:56, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
> > Subject : PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
> > Submitter : Justin P. Mattock<[email protected]>
> > Date : 2009-10-23 16:45 (80 days old)
> > References : http://lkml.org/lkml/2009/10/23/252
> >
> >
> >
>
> I've played around with this. and
> and much confused at what needs to happen.
> (please feedback on what might be happening);
> In any case I can have another try at finding a fix
> so please leave open.
I will, thanks for the update.
Rafael
On Monday 11 January 2010, Arjan van de Ven wrote:
> On Sun, 10 Jan 2010 23:56:13 +0100 (CET)
> "Rafael J. Wysocki" <[email protected]> wrote:
>
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still
> > should be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14657
> > Subject : perf subsystem breakage in 2.6.32-rc7
> > Submitter : Arjan van de Ven <[email protected]>
> > Date : 2009-11-19 19:50 (53 days old)
> > References :
> > http://marc.info/?l=linux-kernel&m=125866013419738&w=4
>
>
> patch available in the bugzilla, and also in
> http://patchwork.kernel.org/patch/71962/
That's in http://bugzilla.kernel.org/show_bug.cgi?id=15040 .
Are they the same bug in fact?
Rafael
On Monday 11 January 2010, Evgeniy Polyakov wrote:
> On Sun, Jan 10, 2010 at 11:56:17PM +0100, Rafael J. Wysocki ([email protected]) wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14894
> > Subject : pohmelfs: NULL pointer dereference
> > Submitter : Alexander Beregalov <[email protected]>
> > Date : 2009-12-02 1:11 (40 days old)
> > References : http://marc.info/?l=linux-kernel&m=125971633107940&w=4
> > Handled-By : Evgeniy Polyakov <[email protected]>
>
> There is a patch to fix the problem, I will test it in a day and push it
> upstrem if it is ok.
Great, thanks a lot!
Rafael
On Monday 11 January 2010, Alan Stern wrote:
> On Sun, 10 Jan 2010, Rafael J. Wysocki wrote:
>
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14896
> > Subject : REGRESSION for RT2561/RT61 in 2.6.32, related to power saving
> > Submitter : Alan Stern <[email protected]>
> > Date : 2009-12-06 22:12 (36 days old)
> > References : http://marc.info/?l=linux-kernel&m=126013756829691&w=4
> > Handled-By : Gertjan van Wingerde <[email protected]>
> > Patch : http://patchwork.kernel.org/patch/67338/
>
> This has been fixed by commit 93b6bd26b74efe46b4579592560f9f1cb7b61994.
Thanks, closing.
Rafael
On Monday 11 January 2010, David John wrote:
> On 01/11/2010 04:26 AM, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14897
> > Subject : i915: Commit 0e442c60 causes flickering
> > Submitter : David John <[email protected]>
> > Date : 2009-12-09 17:26 (33 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c
> > References : http://marc.info/?l=linux-kernel&m=126037889600769&w=4
> >
> >
> >
>
> Still present in 2.6.33-rc3.
Thanks for the update.
Rafael
On Monday 11 January 2010, Robert Hancock wrote:
> On Sun, Jan 10, 2010 at 4:56 PM, Rafael J. Wysocki <[email protected]> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14922
> > Subject : 2.6.32 seemed to have broken nVidia MCP7A sata controller
> > Submitter : Mike Cui <[email protected]>
> > Date : 2009-12-19 6:13 (23 days old)
> > References : http://marc.info/?l=linux-ide&m=126120323407742&w=4
> > Handled-By : Jeff Garzik <[email protected]>
> > Robert Hancock <[email protected]>
>
> Still outstanding. Waiting for testing results from the reporter with
> that drive on another AHCI controller, if possible. I CCed Peer Chen
> from NVIDIA on the Bugzilla report, maybe they know if there is some
> known problem with FPDMA AA on that controller.
Thanks for the update.
Rafael
On Monday 11 January 2010, Rafał Miłecki wrote:
> 2010/1/10 Rafael J. Wysocki <[email protected]>:
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14747
> > Subject : bisected 2.6.32 regression: synaptics touchpad doesn't work
> > Submitter : François Valenduc <[email protected]>
> > Date : 2009-12-06 11:16 (36 days old)
>
> Not sure if this is hackish or not, but some patch exists.
Thanks, updated.
Well, I guess the hackish is rather inevitable in this particular case ...
Rafael
On Monday 11 January 2010, Alan Stern wrote:
> On Sun, 10 Jan 2010, Rafael J. Wysocki wrote:
>
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14841
> > Subject : unable to enumerate USB device on port X after suspend/resume
> > Submitter : Fruhwirth Clemens <[email protected]>
> > Date : 2009-12-19 11:45 (23 days old)
>
> This bug has been resolved as WILL NOT FIX. It ended up having nothing
> to do with suspend or resume, it was caused by strange behavior in the
> device hardware.
Thanks, closed.
Rafael
On Monday 11 January 2010, Jesse Barnes wrote:
> On Mon, 11 Jan 2010 20:03:57 +0100
> Thomas Meyer <[email protected]> wrote:
>
> >
> >
> > Am 11.01.2010 um 17:55 schrieb Jesse Barnes
> > <[email protected]>:
> >
> > > On Mon, 11 Jan 2010 17:53:04 +0100
> > > Thomas Meyer <[email protected]> wrote:
> > >
> > >> Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki:
> > >>> This message has been generated automatically as a part of a
> > >>> report of regressions introduced between 2.6.31 and 2.6.32.
> > >>>
> > >>> The following bug entry is on the current list of known
> > >>> regressions introduced between 2.6.31 and 2.6.32. Please verify
> > >>> if it still should be listed and let me know (either way).
> > >>>
> > >>
> > >> Yes, still should be listed.
> > >>
> > >> Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189,
> > >> that contains
> > >> this commit:
> > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
> > >>
> > >> The above commit removes the render reclock support, that ought to
> > >> fix a common kind of problem encountered on i915 hardware, but not
> > >> on my machine.
> > >>
> > >> Still need to boot with "nomodeset" to have a workable system.
> > >
> > > Does this patch prevent the flicker?
> >
> > By the way: how often and in what interval is the function
> > intel_lvds_detect called?
> >
> > How long will/can the function acpi_lid_open take to complete?
> > Maybe some acpi interpretation takes really long? Is this possible?
> >
> > Would this explain the flickering?
>
> It should only be called when a client requests the connection status
> (e.g. xrandr or the GNOME display applet).
>
> The LVDS state will also be checked at ACPI LID event time, maybe your
> platforms is getting spurious LID events?
>
> If not, this bisection really confuses me...
It's not only a bisection, as Thomas says that reverting the commit turned up
by the bisection fixes the problem for him.
Rafael
On 10.01.2010 23:45, Rafael J. Wysocki wrote:
> This message contains a list of some regressions introduced between 2.6.31 and
> 2.6.32, 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.31
> and 2.6.32, please let me know either and I'll add them to the list.
>
How about #15004?
Cheers, Johannes
Am Montag, den 11.01.2010, 11:19 -0800 schrieb Jesse Barnes:
> On Mon, 11 Jan 2010 20:03:57 +0100
> Thomas Meyer <[email protected]> wrote:
>
> >
> >
> > Am 11.01.2010 um 17:55 schrieb Jesse Barnes
> > <[email protected]>:
> >
> > > On Mon, 11 Jan 2010 17:53:04 +0100
> > > Thomas Meyer <[email protected]> wrote:
> > >
> > >> Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki:
> > >>> This message has been generated automatically as a part of a
> > >>> report of regressions introduced between 2.6.31 and 2.6.32.
> > >>>
> > >>> The following bug entry is on the current list of known
> > >>> regressions introduced between 2.6.31 and 2.6.32. Please verify
> > >>> if it still should be listed and let me know (either way).
> > >>>
> > >>
> > >> Yes, still should be listed.
> > >>
> > >> Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189,
> > >> that contains
> > >> this commit:
> > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
> > >>
> > >> The above commit removes the render reclock support, that ought to
> > >> fix a common kind of problem encountered on i915 hardware, but not
> > >> on my machine.
> > >>
> > >> Still need to boot with "nomodeset" to have a workable system.
> > >
> > > Does this patch prevent the flicker?
> >
> > By the way: how often and in what interval is the function
> > intel_lvds_detect called?
> >
> > How long will/can the function acpi_lid_open take to complete?
> > Maybe some acpi interpretation takes really long? Is this possible?
> >
> > Would this explain the flickering?
>
> It should only be called when a client requests the connection status
> (e.g. xrandr or the GNOME display applet).
how to check how often this function is called and it's duration? is the
function tracer capable of this?
>
> The LVDS state will also be checked at ACPI LID event time, maybe your
> platforms is getting spurious LID events?
maybe! where can I check this? acpid log file?
>
> If not, this bisection really confuses me...
On Tue, 12 Jan 2010 18:43:09 +0100
Thomas Meyer <[email protected]> wrote:
> Am Montag, den 11.01.2010, 11:19 -0800 schrieb Jesse Barnes:
> > On Mon, 11 Jan 2010 20:03:57 +0100
> > Thomas Meyer <[email protected]> wrote:
> >
> > >
> > >
> > > Am 11.01.2010 um 17:55 schrieb Jesse Barnes
> > > <[email protected]>:
> > >
> > > > On Mon, 11 Jan 2010 17:53:04 +0100
> > > > Thomas Meyer <[email protected]> wrote:
> > > >
> > > >> Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J.
> > > >> Wysocki:
> > > >>> This message has been generated automatically as a part of a
> > > >>> report of regressions introduced between 2.6.31 and 2.6.32.
> > > >>>
> > > >>> The following bug entry is on the current list of known
> > > >>> regressions introduced between 2.6.31 and 2.6.32. Please
> > > >>> verify if it still should be listed and let me know (either
> > > >>> way).
> > > >>>
> > > >>
> > > >> Yes, still should be listed.
> > > >>
> > > >> Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189,
> > > >> that contains
> > > >> this commit:
> > > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
> > > >>
> > > >> The above commit removes the render reclock support, that
> > > >> ought to fix a common kind of problem encountered on i915
> > > >> hardware, but not on my machine.
> > > >>
> > > >> Still need to boot with "nomodeset" to have a workable system.
> > > >
> > > > Does this patch prevent the flicker?
> > >
> > > By the way: how often and in what interval is the function
> > > intel_lvds_detect called?
> > >
> > > How long will/can the function acpi_lid_open take to complete?
> > > Maybe some acpi interpretation takes really long? Is this
> > > possible?
> > >
> > > Would this explain the flickering?
> >
> > It should only be called when a client requests the connection
> > status (e.g. xrandr or the GNOME display applet).
>
> how to check how often this function is called and it's duration? is
> the function tracer capable of this?
Yeah, the function tracer should be able to do it (though I don't know
how to use it offhand, maybe through the perf tool?). Or you could
just add some DRM_ERROR lines. :)
> > The LVDS state will also be checked at ACPI LID event time, maybe
> > your platforms is getting spurious LID events?
>
> maybe! where can I check this? acpid log file?
Yeah or using acpi_listen I think.
--
Jesse Barnes, Intel Open Source Technology Center
On Mon, 11 Jan 2010 20:52:57 +0100
"Rafael J. Wysocki" <[email protected]> wrote:
> On Monday 11 January 2010, David John wrote:
> > On 01/11/2010 04:26 AM, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a
> > > report of regressions introduced between 2.6.31 and 2.6.32.
> > >
> > > The following bug entry is on the current list of known
> > > regressions introduced between 2.6.31 and 2.6.32. Please verify
> > > if it still should be listed and let me know (either way).
> > >
> > >
> > > Bug-Entry :
> > > http://bugzilla.kernel.org/show_bug.cgi?id=14897
> > > Subject : i915: Commit 0e442c60 causes flickering
> > > Submitter : David John <[email protected]>
> > > Date : 2009-12-09 17:26 (33 days old)
> > > First-Bad-Commit:
> > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c
> > > References :
> > > http://marc.info/?l=linux-kernel&m=126037889600769&w=4
> > >
> > >
> > >
> >
> > Still present in 2.6.33-rc3.
>
> Thanks for the update.
David I guess you weren't on the bug cc list so you didn't see Yakui's
question. I just attached a patch to it as well. Please check it out.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
On Tuesday 12 January 2010, Johannes Engel wrote:
> On 10.01.2010 23:45, Rafael J. Wysocki wrote:
> > This message contains a list of some regressions introduced between 2.6.31 and
> > 2.6.32, 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.31
> > and 2.6.32, please let me know either and I'll add them to the list.
> >
> How about #15004?
Qualifies, but I need to know the last working kernel.
Rafael
On Mon, Jan 11, 2010 at 6:56 AM, Rafael J. Wysocki <[email protected]> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.31 and 2.6.32.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14903
> Subject : Kernel panic - not syncing: Attempted to kill init!
> Submitter : Zhiyong Wu <[email protected]>
> Date : 2009-12-18 4:08 (24 days old)
> References : http://marc.info/?l=linux-kernel&m=126110931124738&w=4
> Handled-By : Américo Wang <[email protected]>
>
Hi,
I don't think this is a kernel problem, it should be a problem of Zhiyong's
initrd, or Zhiyong may not configure his kernel properly, in any case,
this is not a bug of kernel.
Thanks.
On So, 10 Jan 2010, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14892
> Subject : intel, KMS, suspend2ram resume, screen black
> Submitter : Norbert Preining <[email protected]>
> Date : 2009-11-24 4:35 (48 days old)
> References : http://marc.info/?l=linux-kernel&m=125903731125558&w=4
2.6.33-rc4 contains the patch posted in bugzilla 14722, so I guess that
closes it.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
RUNCORN (n.)
A peeble (q.v.) which is larger that a belper (q.v.)
--- Douglas Adams, The Meaning of Liff
On 01/12/2010 11:44 PM, Jesse Barnes wrote:
> On Mon, 11 Jan 2010 20:52:57 +0100
> "Rafael J. Wysocki" <[email protected]> wrote:
>
>> On Monday 11 January 2010, David John wrote:
>>> On 01/11/2010 04:26 AM, Rafael J. Wysocki wrote:
>>>> This message has been generated automatically as a part of a
>>>> report of regressions introduced between 2.6.31 and 2.6.32.
>>>>
>>>> The following bug entry is on the current list of known
>>>> regressions introduced between 2.6.31 and 2.6.32. Please verify
>>>> if it still should be listed and let me know (either way).
>>>>
>>>>
>>>> Bug-Entry :
>>>> http://bugzilla.kernel.org/show_bug.cgi?id=14897
>>>> Subject : i915: Commit 0e442c60 causes flickering
>>>> Submitter : David John <[email protected]>
>>>> Date : 2009-12-09 17:26 (33 days old)
>>>> First-Bad-Commit:
>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c
>>>> References :
>>>> http://marc.info/?l=linux-kernel&m=126037889600769&w=4
>>>>
>>>>
>>>>
>>>
>>> Still present in 2.6.33-rc3.
>>
>> Thanks for the update.
>
> David I guess you weren't on the bug cc list so you didn't see Yakui's
> question. I just attached a patch to it as well. Please check it out.
>
Hi Jesse,
I've updated the bug report with more info. If you have any other ideas,
I can test those also.
Regards,
David.
Am Dienstag, den 12.01.2010, 09:57 -0800 schrieb Jesse Barnes:
> Yeah, the function tracer should be able to do it (though I don't know
> how to use it offhand, maybe through the perf tool?). Or you could
> just add some DRM_ERROR lines. :)
I set the function tracer to the function "drm_mode_getconnector":
here is the output, that i captured after I start playing a video with
totem (i.e. the flickering starts):
# tracer: function
#
# TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
Xorg-1443 [000] 1880.280581: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.394308: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.395379: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.406780: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.420169: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.424712: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.444334: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.631332: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.632368: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.643349: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.656874: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.662623: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.764168: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.986639: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.988920: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1880.999856: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.013260: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.024310: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.069299: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.303194: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.305308: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.316421: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.329808: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.337493: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.420231: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.633036: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.634075: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.646363: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.659741: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.670751: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.742476: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.959634: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.960669: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.972904: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.986272: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1881.993965: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.078704: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.295050: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.296104: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.309439: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.322834: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.333858: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.407520: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.622870: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.623896: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.635987: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.649366: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.660390: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.772479: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.992680: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1882.993707: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.005845: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.019238: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.026922: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.142571: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.359167: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.360190: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.372398: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.385862: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.393457: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.479378: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.692285: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.693326: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.705552: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.718920: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.729979: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1883.808964: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.032179: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.033222: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.045422: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.058808: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.066525: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.151051: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.368836: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.369872: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.382019: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.395401: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.403100: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.504375: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.725273: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.726373: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.738545: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.751942: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.759633: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1884.828803: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.045242: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.046283: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.058442: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.071842: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.079498: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.162244: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.388404: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.389429: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.401620: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.415130: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.421548: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.510004: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.685747: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.686776: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.698176: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.711599: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.723703: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1885.808301: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.032422: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.033456: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.044685: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.058081: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.065622: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.140785: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.367987: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.369012: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.381254: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.394621: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.402334: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.456423: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.671279: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.672302: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.684470: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.697844: drm_mode_getconnector <-drm_ioctl
Xorg-1443 [000] 1886.705543: drm_mode_getconnector <-drm_ioctl
Any idea why the function "drm_mode_getconnector" is called so many
times?
The call chain seems to be
drm_ioctl ->
drm_mode_getconnector ->
drm_helper_probe_single_connector_modes ->
intel_crt_detect, intel_hdmi_detect and intel_lvds_detect
>
> > > The LVDS state will also be checked at ACPI LID event time, maybe
> > > your platforms is getting spurious LID events?
> >
> > maybe! where can I check this? acpid log file?
>
> Yeah or using acpi_listen I think.
>
acpi lid events seems to correspond to the lid status.
greets
thomas
Am Dienstag, den 12.01.2010, 09:57 -0800 schrieb Jesse Barnes:
> On Tue, 12 Jan 2010 18:43:09 +0100
> Thomas Meyer <[email protected]> wrote:
>
> > Am Montag, den 11.01.2010, 11:19 -0800 schrieb Jesse Barnes:
> > > On Mon, 11 Jan 2010 20:03:57 +0100
> > > Thomas Meyer <[email protected]> wrote:
> > >
> > > >
> > > >
> > > > Am 11.01.2010 um 17:55 schrieb Jesse Barnes
> > > > <[email protected]>:
> > > >
> > > > > On Mon, 11 Jan 2010 17:53:04 +0100
> > > > > Thomas Meyer <[email protected]> wrote:
> > > > >
> > > > >> Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J.
> > > > >> Wysocki:
> > > > >>> This message has been generated automatically as a part of a
> > > > >>> report of regressions introduced between 2.6.31 and 2.6.32.
> > > > >>>
> > > > >>> The following bug entry is on the current list of known
> > > > >>> regressions introduced between 2.6.31 and 2.6.32. Please
> > > > >>> verify if it still should be listed and let me know (either
> > > > >>> way).
> > > > >>>
> > > > >>
> > > > >> Yes, still should be listed.
> > > > >>
> > > > >> Problem still exists in 2.6.32.3 and 2.6.33-rc3-00097-g2c1f189,
> > > > >> that contains
> > > > >> this commit:
> > > > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cda9d05c499093c67b4a376a15009923acc2127a
> > > > >>
> > > > >> The above commit removes the render reclock support, that
> > > > >> ought to fix a common kind of problem encountered on i915
> > > > >> hardware, but not on my machine.
> > > > >>
> > > > >> Still need to boot with "nomodeset" to have a workable system.
> > > > >
> > > > > Does this patch prevent the flicker?
> > > >
> > > > By the way: how often and in what interval is the function
> > > > intel_lvds_detect called?
> > > >
> > > > How long will/can the function acpi_lid_open take to complete?
> > > > Maybe some acpi interpretation takes really long? Is this
> > > > possible?
> > > >
> > > > Would this explain the flickering?
> > >
> > > It should only be called when a client requests the connection
> > > status (e.g. xrandr or the GNOME display applet).
> >
> > how to check how often this function is called and it's duration? is
> > the function tracer capable of this?
>
> Yeah, the function tracer should be able to do it (though I don't know
> how to use it offhand, maybe through the perf tool?). Or you could
> just add some DRM_ERROR lines. :)
After recompiling the kernel without optimize for size I could use the
function graph tracer and set the function to "intel_lvds_detect".
Here is an example of the output:
0) 0.365 us | up();
0) 1.092 us | }
0) 1.824 us | }
0) 2.486 us | }
0) 0.376 us | kfree();
0) ! 9759.012 us | }
0) ! 9759.813 us | }
0) ! 9761.096 us | }
0) ! 9764.483 us | }
0) | intel_lvds_detect() {
0) | acpi_lid_open() {
0) | acpi_evaluate_integer() {
0) | acpi_evaluate_object() {
0) | acpi_os_allocate_zeroed() {
0) | __kmalloc() {
0) 0.366 us | get_slab();
0) 0.336 us | _cond_resched();
0) 0.396 us | memset();
0) 2.796 us | }
0) 3.447 us | }
0) 0.531 us | acpi_ns_validate_handle();
So the call to "intel_lvds_detect" seems to take around 10000us, i.e.
10ms (I guess this is long), thanks to heavy ACPI interpretation.
So the question still is: Why is the drm_ioctl (that in turn calls
intel_lvds_detect) called so often by Xorg?
greets
thomas
On Wednesday 13 January 2010, Norbert Preining wrote:
> On So, 10 Jan 2010, Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14892
> > Subject : intel, KMS, suspend2ram resume, screen black
> > Submitter : Norbert Preining <[email protected]>
> > Date : 2009-11-24 4:35 (48 days old)
> > References : http://marc.info/?l=linux-kernel&m=125903731125558&w=4
>
> 2.6.33-rc4 contains the patch posted in bugzilla 14722, so I guess that
> closes it.
I didn't know it was a dup. Closed now.
Thanks,
Rafael
On Wednesday 13 January 2010, Américo Wang wrote:
> On Mon, Jan 11, 2010 at 6:56 AM, Rafael J. Wysocki <[email protected]> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 2.6.32. Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14903
> > Subject : Kernel panic - not syncing: Attempted to kill init!
> > Submitter : Zhiyong Wu <[email protected]>
> > Date : 2009-12-18 4:08 (24 days old)
> > References : http://marc.info/?l=linux-kernel&m=126110931124738&w=4
> > Handled-By : Américo Wang <[email protected]>
> >
>
> Hi,
>
> I don't think this is a kernel problem, it should be a problem of Zhiyong's
> initrd, or Zhiyong may not configure his kernel properly, in any case,
> this is not a bug of kernel.
Thanks, closing.
Rafael