3.0-rc6-git6: Reported regressions 2.6.38 -> 2.6.39

3.0-rc6-git6: Reported regressions 2.6.38 -> 2.6.39

[Rafael J. Wysocki]

This message contains a list of some post-2.6.38 regressions introduced before
2.6.39, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.

If you know of any other unresolved post-2.6.38 regressions, please let us know
either and we'll add them to the list.  Also, please let us 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
  ----------------------------------------
  2011-07-10       99       26          24
  2011-06-27       94       25          23
  2011-06-12       81       21          18
  2011-05-15       50       12          11
  2011-04-30       38       17          16
  2011-04-17       17       11          10


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38842
Subject		: panic in elv_completed_request on safe remove usb hard drive
Submitter	: leniviy <basinilya@gmail.com>
Date		: 2011-07-06 09:20 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38742
Subject		: After hard power-off, btrfs cannot be recovered except booting 2.6.38 or below kernel
Submitter	: Ryan Underwood <nemesis@icequake.net>
Date		: 2011-07-03 18:57 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38572
Subject		: New NFS: directory XXX contains a readdir loop seems to be triggered by well-behaving server
Submitter	: Petr Vandrovec <petr@vandrovec.name>
Date		: 2011-06-30 19:38 (11 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38132
Subject		: [Warning] 2.6.39.x latencytop
Submitter	: Andrew Watts <akwatts@ymail.com>
Date		: 2011-06-14 17:07 (27 days old)
Message-ID	: <80098.5633.qm@web111013.mail.gq1.yahoo.com>
References	: http://marc.info/?l=linux-kernel&m=130807128506490&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38102
Subject		: BUG kmalloc-2048: Poison overwritten
Submitter	: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Date		: 2011-06-23 17:33 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37772
Subject		: Sometimes, sound disappears and doesn't want to idle.
Submitter	:  <merkil@savhon.org>
Date		: 2011-06-17 22:06 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37752
Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller
Submitter	: Martin Rogge <marogge@onlinehome.de>
Date		: 2011-06-17 13:02 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37712
Subject		: reboot  / "shutdown -r now" hangs ;  works fine on 2.6.38.7-1
Submitter	: Dave Hooper <dave@beermex.com>
Date		: 2011-06-16 20:50 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37692
Subject		: Linux 2.6.39.x fails to boot - unable to mount root fs
Submitter	: Dan Dart <dandart@googlemail.com>
Date		: 2011-06-16 18:55 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37622
Subject		: Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965
Submitter	:  <MDstr_1@hotmail.com>
Date		: 2011-06-16 11:22 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
Subject		: Lenovo U160 (i915 black screen)
Submitter	: Robse <rob-se@live.de>
Date		: 2011-06-14 15:17 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37322
Subject		: high load, unresponsive system spinning in rcu_kthread
Submitter	: Ferenc Wágner <wferi@niif.hu>
Date		: 2011-06-12 14:53 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37312
Subject		: Intel 5100 wifi stopped working with 2.6.39.1
Submitter	: Thibault Dory <dory.thibault@gmail.com>
Date		: 2011-06-12 12:43 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37292
Subject		: kernel BUG at fs/ecryptfs/read_write.c:47!
Submitter	:  <rems14@lestoutous.com>
Date		: 2011-06-12 10:25 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37042
Subject		: linux 3.0.0-rc2 libata-eh.c:4018 ata_scsi_port_error_handler+0x80/0x53d on s2disk
Submitter	: Alex Zhavnerchik <alex.vizor@gmail.com>
Date		: 2011-06-09 08:22 (32 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36952
Subject		: [2.6.39] CIFS write failures where 2.6.38 works
Submitter	: Helge Hafting <helge.hafting@hist.no>
Date		: 2011-06-01 10:11 (40 days old)
Message-ID	: <4DE6103E.6010100@hist.no>
References	: http://marc.info/?l=linux-kernel&m=130692387613423&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36392
Subject		: 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video
Submitter	: Dennis Jansen <dennis.jansen@web.de>
Date		: 2011-06-01 04:41 (40 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36332
Subject		: Intel gpu turns external monitor off when X starts
Submitter	: rocko <rockorequin@hotmail.com>
Date		: 2011-05-31 02:53 (41 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
Subject		: Erroneous package power limit notification since kernel 2.6.39
Submitter	: Olaf Freyer <aaron667@gmx.net>
Date		: 2011-05-22 13:01 (50 days old)
Message-ID	: <4DD9092A.4080507@gmx.net>
References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35922
Subject		: SND_USB_AUDIO recording device not initializing correctly
Submitter	:  <bjoern.online@gmail.com>
Date		: 2011-05-26 10:30 (46 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35662
Subject		: softlockup with kernel 2.6.39
Submitter	: Hussam Al-Tayeb <ht990332@gmail.com>
Date		: 2011-05-23 08:13 (49 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35242
Subject		: NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)
Submitter	: Ko Mi <chaostya.test@hotmail.com>
Date		: 2011-05-17 10:27 (55 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35142
Subject		: 2.6.39-rc7-git1 boot error message (no crash)
Submitter	: werner <w.landgraf@ru.ru>
Date		: 2011-05-11 4:58 (61 days old)
Message-ID	: <web-520830057@zbackend1.aha.ru>
References	: http://marc.info/?l=linux-kernel&m=130512952706444&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=34942
Subject		: [Bug] Kdump does not work when panic triggered due to MCE
Submitter	: K.Prasad <prasad@linux.vnet.ibm.com>
Date		: 2011-05-06 16:54 (66 days old)
Message-ID	: <20110506165412.GB2719@in.ibm.com>
References	: http://marc.info/?l=linux-kernel&m=130470087226270&w=2


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35642
Subject		: On resume, I sometimes get a kernel oops with led_trigger_unregister_simple
Submitter	: Sven-Hendrik Haase <sh@lutzhaase.com>
Date		: 2011-05-23 00:15 (49 days old)
Patch		: https://patchwork.kernel.org/patch/927582/
		  https://patchwork.kernel.org/patch/927612/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=33242
Subject		: Lockdep splat in autofs with 2.6.39-rc2
Submitter	: Nick Bowler <nbowler@elliptictech.com>
Date		: 2011-04-07 19:44 (95 days old)
Message-ID	: <20110407194403.GA29404@elliptictech.com>
References	: http://marc.info/?l=linux-kernel&m=130220545614682&w=2
Patch		: http://marc.info/?l=linux-kernel&m=130342115008659&w=2


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.38 and 2.6.39, unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=32012

Please let the tracking team know if there are any Bugzilla entries that
should be added to the list in there.

Thanks!

3.0-rc6-git6: Reported regressions 2.6.38 -> 2.6.39

[Rafael J. Wysocki]

This message contains a list of some post-2.6.38 regressions introduced before
2.6.39, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.

If you know of any other unresolved post-2.6.38 regressions, please let us know
either and we'll add them to the list.  Also, please let us 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
  ----------------------------------------
  2011-07-10       99       26          24
  2011-06-27       94       25          23
  2011-06-12       81       21          18
  2011-05-15       50       12          11
  2011-04-30       38       17          16
  2011-04-17       17       11          10


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38842
Subject		: panic in elv_completed_request on safe remove usb hard drive
Submitter	: leniviy <basinilya-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-07-06 09:20 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38742
Subject		: After hard power-off, btrfs cannot be recovered except booting 2.6.38 or below kernel
Submitter	: Ryan Underwood <nemesis-RBwgCYbvQ+vk1uMJSBkQmQ@public.gmane.org>
Date		: 2011-07-03 18:57 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38572
Subject		: New NFS: directory XXX contains a readdir loop seems to be triggered by well-behaving server
Submitter	: Petr Vandrovec <petr-vPk2MGR0e28uaRcfnNAh7A@public.gmane.org>
Date		: 2011-06-30 19:38 (11 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38132
Subject		: [Warning] 2.6.39.x latencytop
Submitter	: Andrew Watts <akwatts-DaQTI0RpDDMAvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-14 17:07 (27 days old)
Message-ID	: <80098.5633.qm-tGSp4LqzbTn6X00i2u5GFvu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130807128506490&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38102
Subject		: BUG kmalloc-2048: Poison overwritten
Submitter	: Alexey Zaytsev <alexey.zaytsev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-23 17:33 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37772
Subject		: Sometimes, sound disappears and doesn't want to idle.
Submitter	:  <merkil-kt3qwsSULN8dnm+yROfE0A@public.gmane.org>
Date		: 2011-06-17 22:06 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37752
Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller
Submitter	: Martin Rogge <marogge-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
Date		: 2011-06-17 13:02 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37712
Subject		: reboot  / "shutdown -r now" hangs ;  works fine on 2.6.38.7-1
Submitter	: Dave Hooper <dave-kId6I2PxnVtBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-06-16 20:50 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37692
Subject		: Linux 2.6.39.x fails to boot - unable to mount root fs
Submitter	: Dan Dart <dandart-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date		: 2011-06-16 18:55 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37622
Subject		: Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965
Submitter	:  <MDstr_1-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-06-16 11:22 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
Subject		: Lenovo U160 (i915 black screen)
Submitter	: Robse <rob-se-Dz115AEZgoU@public.gmane.org>
Date		: 2011-06-14 15:17 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37322
Subject		: high load, unresponsive system spinning in rcu_kthread
Submitter	: Ferenc Wágner <wferi-eEbw3PyuezQ@public.gmane.org>
Date		: 2011-06-12 14:53 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37312
Subject		: Intel 5100 wifi stopped working with 2.6.39.1
Submitter	: Thibault Dory <dory.thibault-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-12 12:43 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37292
Subject		: kernel BUG at fs/ecryptfs/read_write.c:47!
Submitter	:  <rems14-fqJXh2VwIQ9ByuSxxbvQtw@public.gmane.org>
Date		: 2011-06-12 10:25 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37042
Subject		: linux 3.0.0-rc2 libata-eh.c:4018 ata_scsi_port_error_handler+0x80/0x53d on s2disk
Submitter	: Alex Zhavnerchik <alex.vizor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-09 08:22 (32 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36952
Subject		: [2.6.39] CIFS write failures where 2.6.38 works
Submitter	: Helge Hafting <helge.hafting-CND4fxrytsY@public.gmane.org>
Date		: 2011-06-01 10:11 (40 days old)
Message-ID	: <4DE6103E.6010100-CND4fxrytsY@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130692387613423&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36392
Subject		: 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video
Submitter	: Dennis Jansen <dennis.jansen-S0/GAf8tV78@public.gmane.org>
Date		: 2011-06-01 04:41 (40 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36332
Subject		: Intel gpu turns external monitor off when X starts
Submitter	: rocko <rockorequin-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-05-31 02:53 (41 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
Subject		: Erroneous package power limit notification since kernel 2.6.39
Submitter	: Olaf Freyer <aaron667-hi6Y0CQ0nG0@public.gmane.org>
Date		: 2011-05-22 13:01 (50 days old)
Message-ID	: <4DD9092A.4080507-hi6Y0CQ0nG0@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35922
Subject		: SND_USB_AUDIO recording device not initializing correctly
Submitter	:  <bjoern.online-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-05-26 10:30 (46 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35662
Subject		: softlockup with kernel 2.6.39
Submitter	: Hussam Al-Tayeb <ht990332-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-05-23 08:13 (49 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35242
Subject		: NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)
Submitter	: Ko Mi <chaostya.test-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-05-17 10:27 (55 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35142
Subject		: 2.6.39-rc7-git1 boot error message (no crash)
Submitter	: werner <w.landgraf-ow1r9FSYgO0@public.gmane.org>
Date		: 2011-05-11 4:58 (61 days old)
Message-ID	: <web-520830057-zcyLqNHFQq3Ee+7He9zlJw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130512952706444&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=34942
Subject		: [Bug] Kdump does not work when panic triggered due to MCE
Submitter	: K.Prasad <prasad-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date		: 2011-05-06 16:54 (66 days old)
Message-ID	: <20110506165412.GB2719-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130470087226270&w=2


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35642
Subject		: On resume, I sometimes get a kernel oops with led_trigger_unregister_simple
Submitter	: Sven-Hendrik Haase <sh-5wni8d9J0yJl57MIdRCFDg@public.gmane.org>
Date		: 2011-05-23 00:15 (49 days old)
Patch		: https://patchwork.kernel.org/patch/927582/
		  https://patchwork.kernel.org/patch/927612/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=33242
Subject		: Lockdep splat in autofs with 2.6.39-rc2
Submitter	: Nick Bowler <nbowler-7BP4RkwGw0uXmMXjJBpWqg@public.gmane.org>
Date		: 2011-04-07 19:44 (95 days old)
Message-ID	: <20110407194403.GA29404-7BP4RkwGw0uXmMXjJBpWqg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130220545614682&w=2
Patch		: http://marc.info/?l=linux-kernel&m=130342115008659&w=2


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.38 and 2.6.39, unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=32012

Please let the tracking team know if there are any Bugzilla entries that
should be added to the list in there.

Thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

3.0-rc6-git6: Reported regressions 2.6.38 -> 2.6.39

[Rafael J. Wysocki]

This message contains a list of some post-2.6.38 regressions introduced before
2.6.39, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.

If you know of any other unresolved post-2.6.38 regressions, please let us know
either and we'll add them to the list.  Also, please let us 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
  ----------------------------------------
  2011-07-10       99       26          24
  2011-06-27       94       25          23
  2011-06-12       81       21          18
  2011-05-15       50       12          11
  2011-04-30       38       17          16
  2011-04-17       17       11          10


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38842
Subject		: panic in elv_completed_request on safe remove usb hard drive
Submitter	: leniviy <basinilya-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-07-06 09:20 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38742
Subject		: After hard power-off, btrfs cannot be recovered except booting 2.6.38 or below kernel
Submitter	: Ryan Underwood <nemesis-RBwgCYbvQ+vk1uMJSBkQmQ@public.gmane.org>
Date		: 2011-07-03 18:57 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38572
Subject		: New NFS: directory XXX contains a readdir loop seems to be triggered by well-behaving server
Submitter	: Petr Vandrovec <petr-vPk2MGR0e28uaRcfnNAh7A@public.gmane.org>
Date		: 2011-06-30 19:38 (11 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38132
Subject		: [Warning] 2.6.39.x latencytop
Submitter	: Andrew Watts <akwatts-DaQTI0RpDDMAvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-14 17:07 (27 days old)
Message-ID	: <80098.5633.qm-tGSp4LqzbTn6X00i2u5GFvu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130807128506490&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38102
Subject		: BUG kmalloc-2048: Poison overwritten
Submitter	: Alexey Zaytsev <alexey.zaytsev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-23 17:33 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37772
Subject		: Sometimes, sound disappears and doesn't want to idle.
Submitter	:  <merkil-kt3qwsSULN8dnm+yROfE0A@public.gmane.org>
Date		: 2011-06-17 22:06 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37752
Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller
Submitter	: Martin Rogge <marogge-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
Date		: 2011-06-17 13:02 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37712
Subject		: reboot  / "shutdown -r now" hangs ;  works fine on 2.6.38.7-1
Submitter	: Dave Hooper <dave-kId6I2PxnVtBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-06-16 20:50 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37692
Subject		: Linux 2.6.39.x fails to boot - unable to mount root fs
Submitter	: Dan Dart <dandart-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date		: 2011-06-16 18:55 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37622
Subject		: Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965
Submitter	:  <MDstr_1-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-06-16 11:22 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
Subject		: Lenovo U160 (i915 black screen)
Submitter	: Robse <rob-se-Dz115AEZgoU@public.gmane.org>
Date		: 2011-06-14 15:17 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37322
Subject		: high load, unresponsive system spinning in rcu_kthread
Submitter	: Ferenc Wágner <wferi-eEbw3PyuezQ@public.gmane.org>
Date		: 2011-06-12 14:53 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37312
Subject		: Intel 5100 wifi stopped working with 2.6.39.1
Submitter	: Thibault Dory <dory.thibault-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-12 12:43 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37292
Subject		: kernel BUG at fs/ecryptfs/read_write.c:47!
Submitter	:  <rems14-fqJXh2VwIQ9ByuSxxbvQtw@public.gmane.org>
Date		: 2011-06-12 10:25 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37042
Subject		: linux 3.0.0-rc2 libata-eh.c:4018 ata_scsi_port_error_handler+0x80/0x53d on s2disk
Submitter	: Alex Zhavnerchik <alex.vizor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-09 08:22 (32 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36952
Subject		: [2.6.39] CIFS write failures where 2.6.38 works
Submitter	: Helge Hafting <helge.hafting-CND4fxrytsY@public.gmane.org>
Date		: 2011-06-01 10:11 (40 days old)
Message-ID	: <4DE6103E.6010100-CND4fxrytsY@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130692387613423&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36392
Subject		: 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video
Submitter	: Dennis Jansen <dennis.jansen-S0/GAf8tV78@public.gmane.org>
Date		: 2011-06-01 04:41 (40 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36332
Subject		: Intel gpu turns external monitor off when X starts
Submitter	: rocko <rockorequin-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-05-31 02:53 (41 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
Subject		: Erroneous package power limit notification since kernel 2.6.39
Submitter	: Olaf Freyer <aaron667-hi6Y0CQ0nG0@public.gmane.org>
Date		: 2011-05-22 13:01 (50 days old)
Message-ID	: <4DD9092A.4080507-hi6Y0CQ0nG0@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35922
Subject		: SND_USB_AUDIO recording device not initializing correctly
Submitter	:  <bjoern.online-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-05-26 10:30 (46 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35662
Subject		: softlockup with kernel 2.6.39
Submitter	: Hussam Al-Tayeb <ht990332-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-05-23 08:13 (49 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35242
Subject		: NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)
Submitter	: Ko Mi <chaostya.test-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-05-17 10:27 (55 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35142
Subject		: 2.6.39-rc7-git1 boot error message (no crash)
Submitter	: werner <w.landgraf-ow1r9FSYgO0@public.gmane.org>
Date		: 2011-05-11 4:58 (61 days old)
Message-ID	: <web-520830057-zcyLqNHFQq3Ee+7He9zlJw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130512952706444&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=34942
Subject		: [Bug] Kdump does not work when panic triggered due to MCE
Submitter	: K.Prasad <prasad-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date		: 2011-05-06 16:54 (66 days old)
Message-ID	: <20110506165412.GB2719-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130470087226270&w=2


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35642
Subject		: On resume, I sometimes get a kernel oops with led_trigger_unregister_simple
Submitter	: Sven-Hendrik Haase <sh-5wni8d9J0yJl57MIdRCFDg@public.gmane.org>
Date		: 2011-05-23 00:15 (49 days old)
Patch		: https://patchwork.kernel.org/patch/927582/
		  https://patchwork.kernel.org/patch/927612/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=33242
Subject		: Lockdep splat in autofs with 2.6.39-rc2
Submitter	: Nick Bowler <nbowler-7BP4RkwGw0uXmMXjJBpWqg@public.gmane.org>
Date		: 2011-04-07 19:44 (95 days old)
Message-ID	: <20110407194403.GA29404-7BP4RkwGw0uXmMXjJBpWqg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130220545614682&w=2
Patch		: http://marc.info/?l=linux-kernel&m=130342115008659&w=2


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.38 and 2.6.39, unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=32012

Please let the tracking team know if there are any Bugzilla entries that
should be added to the list in there.

Thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug #33242] Lockdep splat in autofs with 2.6.39-rc2

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=33242
Subject		: Lockdep splat in autofs with 2.6.39-rc2
Submitter	: Nick Bowler <nbowler@elliptictech.com>
Date		: 2011-04-07 19:44 (95 days old)
Message-ID	: <20110407194403.GA29404@elliptictech.com>
References	: http://marc.info/?l=linux-kernel&m=130220545614682&w=2
Patch		: http://marc.info/?l=linux-kernel&m=130342115008659&w=2

[Bug #35142] 2.6.39-rc7-git1 boot error message (no crash)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35142
Subject		: 2.6.39-rc7-git1 boot error message (no crash)
Submitter	: werner <w.landgraf@ru.ru>
Date		: 2011-05-11 4:58 (61 days old)
Message-ID	: <web-520830057@zbackend1.aha.ru>
References	: http://marc.info/?l=linux-kernel&m=130512952706444&w=2

[Bug #35242] NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35242
Subject		: NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)
Submitter	: Ko Mi <chaostya.test@hotmail.com>
Date		: 2011-05-17 10:27 (55 days old)

[Bug #35662] softlockup with kernel 2.6.39

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35662
Subject		: softlockup with kernel 2.6.39
Submitter	: Hussam Al-Tayeb <ht990332@gmail.com>
Date		: 2011-05-23 08:13 (49 days old)

[Bug #35642] On resume, I sometimes get a kernel oops with led_trigger_unregister_simple

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35642
Subject		: On resume, I sometimes get a kernel oops with led_trigger_unregister_simple
Submitter	: Sven-Hendrik Haase <sh@lutzhaase.com>
Date		: 2011-05-23 00:15 (49 days old)
Patch		: https://patchwork.kernel.org/patch/927582/
		  https://patchwork.kernel.org/patch/927612/

[Bug #34942] [Bug] Kdump does not work when panic triggered due to MCE

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=34942
Subject		: [Bug] Kdump does not work when panic triggered due to MCE
Submitter	: K.Prasad <prasad@linux.vnet.ibm.com>
Date		: 2011-05-06 16:54 (66 days old)
Message-ID	: <20110506165412.GB2719@in.ibm.com>
References	: http://marc.info/?l=linux-kernel&m=130470087226270&w=2

[Bug #35642] On resume, I sometimes get a kernel oops with led_trigger_unregister_simple

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35642
Subject		: On resume, I sometimes get a kernel oops with led_trigger_unregister_simple
Submitter	: Sven-Hendrik Haase <sh-5wni8d9J0yJl57MIdRCFDg@public.gmane.org>
Date		: 2011-05-23 00:15 (49 days old)
Patch		: https://patchwork.kernel.org/patch/927582/
		  https://patchwork.kernel.org/patch/927612/

[Bug #35662] softlockup with kernel 2.6.39

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35662
Subject		: softlockup with kernel 2.6.39
Submitter	: Hussam Al-Tayeb <ht990332-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-05-23 08:13 (49 days old)

[Bug #35242] NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35242
Subject		: NULL pointer dereference in intel_sdvo_write_cmd (was Black screen after boot)
Submitter	: Ko Mi <chaostya.test-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2011-05-17 10:27 (55 days old)

[Bug #34942] [Bug] Kdump does not work when panic triggered due to MCE

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=34942
Subject		: [Bug] Kdump does not work when panic triggered due to MCE
Submitter	: K.Prasad <prasad-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date		: 2011-05-06 16:54 (66 days old)
Message-ID	: <20110506165412.GB2719-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=130470087226270&w=2

[Bug #36392] 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36392
Subject		: 2.6.39, 3.0-rc2 Intel DRI Regression: Black Screen after trying to play video
Submitter	: Dennis Jansen <dennis.jansen@web.de>
Date		: 2011-06-01 04:41 (40 days old)

[Bug #36332] Intel gpu turns external monitor off when X starts

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36332
Subject		: Intel gpu turns external monitor off when X starts
Submitter	: rocko <rockorequin@hotmail.com>
Date		: 2011-05-31 02:53 (41 days old)

[Bug #35922] SND_USB_AUDIO recording device not initializing correctly

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35922
Subject		: SND_USB_AUDIO recording device not initializing correctly
Submitter	:  <bjoern.online@gmail.com>
Date		: 2011-05-26 10:30 (46 days old)

[Bug #36182] Erroneous package power limit notification since kernel 2.6.39

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
Subject		: Erroneous package power limit notification since kernel 2.6.39
Submitter	: Olaf Freyer <aaron667@gmx.net>
Date		: 2011-05-22 13:01 (50 days old)
Message-ID	: <4DD9092A.4080507@gmx.net>
References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2

[Bug #35922] SND_USB_AUDIO recording device not initializing correctly

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=35922
Subject		: SND_USB_AUDIO recording device not initializing correctly
Submitter	:  <bjoern.online-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-05-26 10:30 (46 days old)

[Bug #37042] linux 3.0.0-rc2 libata-eh.c:4018 ata_scsi_port_error_handler+0x80/0x53d on s2disk

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37042
Subject		: linux 3.0.0-rc2 libata-eh.c:4018 ata_scsi_port_error_handler+0x80/0x53d on s2disk
Submitter	: Alex Zhavnerchik <alex.vizor@gmail.com>
Date		: 2011-06-09 08:22 (32 days old)

[Bug #37292] kernel BUG at fs/ecryptfs/read_write.c:47!

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37292
Subject		: kernel BUG at fs/ecryptfs/read_write.c:47!
Submitter	:  <rems14@lestoutous.com>
Date		: 2011-06-12 10:25 (29 days old)

[Bug #37312] Intel 5100 wifi stopped working with 2.6.39.1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37312
Subject		: Intel 5100 wifi stopped working with 2.6.39.1
Submitter	: Thibault Dory <dory.thibault@gmail.com>
Date		: 2011-06-12 12:43 (29 days old)

[Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36952
Subject		: [2.6.39] CIFS write failures where 2.6.38 works
Submitter	: Helge Hafting <helge.hafting@hist.no>
Date		: 2011-06-01 10:11 (40 days old)
Message-ID	: <4DE6103E.6010100@hist.no>
References	: http://marc.info/?l=linux-kernel&m=130692387613423&w=2

[Bug #37292] kernel BUG at fs/ecryptfs/read_write.c:47!

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37292
Subject		: kernel BUG at fs/ecryptfs/read_write.c:47!
Submitter	:  <rems14@lestoutous.com>
Date		: 2011-06-12 10:25 (29 days old)

[Bug #37322] high load, unresponsive system spinning in rcu_kthread

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37322
Subject		: high load, unresponsive system spinning in rcu_kthread
Submitter	: Ferenc Wágner <wferi@niif.hu>
Date		: 2011-06-12 14:53 (29 days old)

[Bug #37622] Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37622
Subject		: Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965
Submitter	:  <MDstr_1@hotmail.com>
Date		: 2011-06-16 11:22 (25 days old)

[Bug #37692] Linux 2.6.39.x fails to boot - unable to mount root fs

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37692
Subject		: Linux 2.6.39.x fails to boot - unable to mount root fs
Submitter	: Dan Dart <dandart@googlemail.com>
Date		: 2011-06-16 18:55 (25 days old)

[Bug #37472] Lenovo U160 (i915 black screen)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
Subject		: Lenovo U160 (i915 black screen)
Submitter	: Robse <rob-se@live.de>
Date		: 2011-06-14 15:17 (27 days old)

[Bug #37322] high load, unresponsive system spinning in rcu_kthread

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37322
Subject		: high load, unresponsive system spinning in rcu_kthread
Submitter	: Ferenc Wágner <wferi@niif.hu>
Date		: 2011-06-12 14:53 (29 days old)

[Bug #37692] Linux 2.6.39.x fails to boot - unable to mount root fs

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37692
Subject		: Linux 2.6.39.x fails to boot - unable to mount root fs
Submitter	: Dan Dart <dandart-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date		: 2011-06-16 18:55 (25 days old)

[Bug #37622] Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37622
Subject		: Poor wireless performance with Intel 4965AGN with iwl-legacy/iwl4965
Submitter	:  <MDstr_1@hotmail.com>
Date		: 2011-06-16 11:22 (25 days old)

[Bug #37752] Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37752
Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller
Submitter	: Martin Rogge <marogge@onlinehome.de>
Date		: 2011-06-17 13:02 (24 days old)

[Bug #37772] Sometimes, sound disappears and doesn't want to idle.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37772
Subject		: Sometimes, sound disappears and doesn't want to idle.
Submitter	:  <merkil@savhon.org>
Date		: 2011-06-17 22:06 (24 days old)

[Bug #37712] reboot / "shutdown -r now" hangs ; works fine on 2.6.38.7-1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37712
Subject		: reboot  / "shutdown -r now" hangs ;  works fine on 2.6.38.7-1
Submitter	: Dave Hooper <dave@beermex.com>
Date		: 2011-06-16 20:50 (25 days old)

[Bug #37772] Sometimes, sound disappears and doesn't want to idle.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37772
Subject		: Sometimes, sound disappears and doesn't want to idle.
Submitter	:  <merkil@savhon.org>
Date		: 2011-06-17 22:06 (24 days old)

[Bug #38102] BUG kmalloc-2048: Poison overwritten

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38102
Subject		: BUG kmalloc-2048: Poison overwritten
Submitter	: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Date		: 2011-06-23 17:33 (18 days old)

[Bug #38132] [Warning] 2.6.39.x latencytop

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38132
Subject		: [Warning] 2.6.39.x latencytop
Submitter	: Andrew Watts <akwatts@ymail.com>
Date		: 2011-06-14 17:07 (27 days old)
Message-ID	: <80098.5633.qm@web111013.mail.gq1.yahoo.com>
References	: http://marc.info/?l=linux-kernel&m=130807128506490&w=2

[Bug #38102] BUG kmalloc-2048: Poison overwritten

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38102
Subject		: BUG kmalloc-2048: Poison overwritten
Submitter	: Alexey Zaytsev <alexey.zaytsev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2011-06-23 17:33 (18 days old)

[Bug #38842] panic in elv_completed_request on safe remove usb hard drive

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38842
Subject		: panic in elv_completed_request on safe remove usb hard drive
Submitter	: leniviy <basinilya@gmail.com>
Date		: 2011-07-06 09:20 (5 days old)

[Bug #38742] After hard power-off, btrfs cannot be recovered except booting 2.6.38 or below kernel

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=38742
Subject		: After hard power-off, btrfs cannot be recovered except booting 2.6.38 or below kernel
Submitter	: Ryan Underwood <nemesis@icequake.net>
Date		: 2011-07-03 18:57 (8 days old)

Re: [Bug #38102] BUG kmalloc-2048: Poison overwritten

[Alexey Zaytsev]

On Sun, Jul 10, 2011 at 14:58, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).

Hey.

This is not a regression, it's been this way since at least since
2.6.27 (checked), and probably from the beginning.

>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38102
> Subject         : BUG kmalloc-2048: Poison overwritten
> Submitter       : Alexey Zaytsev <alexey.zaytsev@gmail.com>
> Date            : 2011-06-23 17:33 (18 days old)
>
>
>

Re: [Bug #38102] BUG kmalloc-2048: Poison overwritten

[Alexey Zaytsev]

On Sun, Jul 10, 2011 at 14:58, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).

Hey.

This is not a regression, it's been this way since at least since
2.6.27 (checked), and probably from the beginning.

>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38102
> Subject         : BUG kmalloc-2048: Poison overwritten
> Submitter       : Alexey Zaytsev <alexey.zaytsev@gmail.com>
> Date            : 2011-06-23 17:33 (18 days old)
>
>
>

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Pekka Enberg]

On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
> Subject         : [Warning] 2.6.39.x latencytop
> Submitter       : Andrew Watts <akwatts@ymail.com>
> Date            : 2011-06-14 17:07 (27 days old)
> Message-ID      : <80098.5633.qm@web111013.mail.gq1.yahoo.com>
> References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2

This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
tracing_enabled for tracing_on") that lets the user know about
deprecated ABI. It's somewhat unfortunate that there's no mention in
the changelog if everyone agreed on the deprecation or not...

That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
I think this issue can be closed.

                        Pekka

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Pekka Enberg]

On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=37472
> Subject         : Lenovo U160 (i915 black screen)
> Submitter       : Robse <rob-se@live.de>
> Date            : 2011-06-14 15:17 (27 days old)

There's no mention that the i915 developers know about this problem so
I'm CC'ing Keith and Chris.

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Pekka Enberg]

On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=37472
> Subject         : Lenovo U160 (i915 black screen)
> Submitter       : Robse <rob-se-Dz115AEZgoU@public.gmane.org>
> Date            : 2011-06-14 15:17 (27 days old)

There's no mention that the i915 developers know about this problem so
I'm CC'ing Keith and Chris.

Re: [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Pekka Enberg]

On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=36952
> Subject         : [2.6.39] CIFS write failures where 2.6.38 works
> Submitter       : Helge Hafting <helge.hafting@hist.no>
> Date            : 2011-06-01 10:11 (40 days old)
> Message-ID      : <4DE6103E.6010100@hist.no>
> References      : http://marc.info/?l=linux-kernel&m=130692387613423&w=2

The last comment in Bugzilla states that Jeff was working on a patch.
Was it ever submitted to mainline and stable?

                                Pekka

Re: [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Pekka Enberg]

On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=36952
> Subject         : [2.6.39] CIFS write failures where 2.6.38 works
> Submitter       : Helge Hafting <helge.hafting-CND4fxrytsY@public.gmane.org>
> Date            : 2011-06-01 10:11 (40 days old)
> Message-ID      : <4DE6103E.6010100-CND4fxrytsY@public.gmane.org>
> References      : http://marc.info/?l=linux-kernel&m=130692387613423&w=2

The last comment in Bugzilla states that Jeff was working on a patch.
Was it ever submitted to mainline and stable?

                                Pekka

Re: [Bug #34942] [Bug] Kdump does not work when panic triggered due to MCE

[Pekka Enberg]

On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=34942
> Subject         : [Bug] Kdump does not work when panic triggered due to MCE
> Submitter       : K.Prasad <prasad@linux.vnet.ibm.com>
> Date            : 2011-05-06 16:54 (66 days old)
> Message-ID      : <20110506165412.GB2719@in.ibm.com>
> References      : http://marc.info/?l=linux-kernel&m=130470087226270&w=2

There's actually no mention that kdump worked with MCE in 2.6.38
either. So is this really a regression?

                        Pekka

Re: [Bug #34942] [Bug] Kdump does not work when panic triggered due to MCE

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Pekka Enberg wrote:
> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=34942
> > Subject         : [Bug] Kdump does not work when panic triggered due to MCE
> > Submitter       : K.Prasad <prasad@linux.vnet.ibm.com>
> > Date            : 2011-05-06 16:54 (66 days old)
> > Message-ID      : <20110506165412.GB2719@in.ibm.com>
> > References      : http://marc.info/?l=linux-kernel&m=130470087226270&w=2
> 
> There's actually no mention that kdump worked with MCE in 2.6.38
> either. So is this really a regression?

Well, for us it's easier to assume a regression and drop it from the list
when it turns out not to be one.  I guess that's happend this time, so
the submitter is kindly asked to speak. :-)

Thanks,
Rafael

Re: [Bug #34942] [Bug] Kdump does not work when panic triggered due to MCE

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Pekka Enberg wrote:
> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=34942
> > Subject         : [Bug] Kdump does not work when panic triggered due to MCE
> > Submitter       : K.Prasad <prasad-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> > Date            : 2011-05-06 16:54 (66 days old)
> > Message-ID      : <20110506165412.GB2719-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
> > References      : http://marc.info/?l=linux-kernel&m=130470087226270&w=2
> 
> There's actually no mention that kdump worked with MCE in 2.6.38
> either. So is this really a regression?

Well, for us it's easier to assume a regression and drop it from the list
when it turns out not to be one.  I guess that's happend this time, so
the submitter is kindly asked to speak. :-)

Thanks,
Rafael

Re: [Bug #38102] BUG kmalloc-2048: Poison overwritten

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Alexey Zaytsev wrote:
> On Sun, Jul 10, 2011 at 14:58, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> 
> Hey.
> 
> This is not a regression, it's been this way since at least since
> 2.6.27 (checked), and probably from the beginning.

Thanks, dropping from the list.

Rafael

Re: [Bug #38102] BUG kmalloc-2048: Poison overwritten

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Alexey Zaytsev wrote:
> On Sun, Jul 10, 2011 at 14:58, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> 
> Hey.
> 
> This is not a regression, it's been this way since at least since
> 2.6.27 (checked), and probably from the beginning.

Thanks, dropping from the list.

Rafael

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Pekka Enberg wrote:
> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
> > Subject         : [Warning] 2.6.39.x latencytop
> > Submitter       : Andrew Watts <akwatts@ymail.com>
> > Date            : 2011-06-14 17:07 (27 days old)
> > Message-ID      : <80098.5633.qm@web111013.mail.gq1.yahoo.com>
> > References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2
> 
> This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
> tracing_enabled for tracing_on") that lets the user know about
> deprecated ABI. It's somewhat unfortunate that there's no mention in
> the changelog if everyone agreed on the deprecation or not...
> 
> That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
> I think this issue can be closed.

OK

Rafael

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Pekka Enberg wrote:
> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
> > Subject         : [Warning] 2.6.39.x latencytop
> > Submitter       : Andrew Watts <akwatts-DaQTI0RpDDMAvxtiuMwx3w@public.gmane.org>
> > Date            : 2011-06-14 17:07 (27 days old)
> > Message-ID      : <80098.5633.qm-tGSp4LqzbTn6X00i2u5GFvu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
> > References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2
> 
> This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
> tracing_enabled for tracing_on") that lets the user know about
> deprecated ABI. It's somewhat unfortunate that there's no mention in
> the changelog if everyone agreed on the deprecation or not...
> 
> That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
> I think this issue can be closed.

OK

Rafael

Re: [Bug #36182] Erroneous package power limit notification since kernel 2.6.39

[Olaf Freyer]

This issue is still worth listing, as it isn't resolved yet.

Jesse Barnes already tracked down the cause to commit
ccab5c82759e2ace74b2e84f82d1e0eedd932571 -
but what to do now remains unclear to me.

With the patch reverted, I get down to 1 warning per workday -
without reverting it I'm at 70-90k warnings per workday.


Am 10.07.2011 12:58, schrieb Rafael J. Wysocki:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
> Subject		: Erroneous package power limit notification since kernel 2.6.39
> Submitter	: Olaf Freyer <aaron667@gmx.net>
> Date		: 2011-05-22 13:01 (50 days old)
> Message-ID	: <4DD9092A.4080507@gmx.net>
> References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2
>
>
>

Re: [Bug #36182] Erroneous package power limit notification since kernel 2.6.39

[Olaf Freyer]

This issue is still worth listing, as it isn't resolved yet.

Jesse Barnes already tracked down the cause to commit
ccab5c82759e2ace74b2e84f82d1e0eedd932571 -
but what to do now remains unclear to me.

With the patch reverted, I get down to 1 warning per workday -
without reverting it I'm at 70-90k warnings per workday.


Am 10.07.2011 12:58, schrieb Rafael J. Wysocki:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
> Subject		: Erroneous package power limit notification since kernel 2.6.39
> Submitter	: Olaf Freyer <aaron667-hi6Y0CQ0nG0@public.gmane.org>
> Date		: 2011-05-22 13:01 (50 days old)
> Message-ID	: <4DD9092A.4080507-hi6Y0CQ0nG0@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2
>
>
>

Re: [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Jeff Layton]

On Sun, 10 Jul 2011 14:58:54 +0300
Pekka Enberg <penberg@kernel.org> wrote:

> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=36952
> > Subject         : [2.6.39] CIFS write failures where 2.6.38 works
> > Submitter       : Helge Hafting <helge.hafting@hist.no>
> > Date            : 2011-06-01 10:11 (40 days old)
> > Message-ID      : <4DE6103E.6010100@hist.no>
> > References      : http://marc.info/?l=linux-kernel&m=130692387613423&w=2
> 
> The last comment in Bugzilla states that Jeff was working on a patch.
> Was it ever submitted to mainline and stable?
> 
>                                 Pekka

Yes, see commit 1190f6a067b in mainline. I also backported it for
2.6.39-stable and sent it to stable@kernel.org, but I haven't heard
anything back on it yet (I'll resend if I don't hear anything in the
next day or two).

-- 
Jeff Layton <jlayton@redhat.com>

Re: [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Jeff Layton]

On Sun, 10 Jul 2011 14:58:54 +0300
Pekka Enberg <penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:

> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=36952
> > Subject         : [2.6.39] CIFS write failures where 2.6.38 works
> > Submitter       : Helge Hafting <helge.hafting@hist.no>
> > Date            : 2011-06-01 10:11 (40 days old)
> > Message-ID      : <4DE6103E.6010100-CND4fxrytsY@public.gmane.org>
> > References      : http://marc.info/?l=linux-kernel&m=130692387613423&w=2
> 
> The last comment in Bugzilla states that Jeff was working on a patch.
> Was it ever submitted to mainline and stable?
> 
>                                 Pekka

Yes, see commit 1190f6a067b in mainline. I also backported it for
2.6.39-stable and sent it to stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, but I haven't heard
anything back on it yet (I'll resend if I don't hear anything in the
next day or two).

-- 
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Re: [Bug #36182] Erroneous package power limit notification since kernel 2.6.39

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Olaf Freyer wrote:
> This issue is still worth listing, as it isn't resolved yet.
> 
> Jesse Barnes already tracked down the cause to commit
> ccab5c82759e2ace74b2e84f82d1e0eedd932571 -
> but what to do now remains unclear to me.
> 
> With the patch reverted, I get down to 1 warning per workday -
> without reverting it I'm at 70-90k warnings per workday.

Thanks for the update.

Rafael


> Am 10.07.2011 12:58, schrieb Rafael J. Wysocki:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
> > Subject		: Erroneous package power limit notification since kernel 2.6.39
> > Submitter	: Olaf Freyer <aaron667@gmx.net>
> > Date		: 2011-05-22 13:01 (50 days old)
> > Message-ID	: <4DD9092A.4080507@gmx.net>
> > References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2
> >
> >
> >
> 
> 
> 

Re: [Bug #36182] Erroneous package power limit notification since kernel 2.6.39

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Olaf Freyer wrote:
> This issue is still worth listing, as it isn't resolved yet.
> 
> Jesse Barnes already tracked down the cause to commit
> ccab5c82759e2ace74b2e84f82d1e0eedd932571 -
> but what to do now remains unclear to me.
> 
> With the patch reverted, I get down to 1 warning per workday -
> without reverting it I'm at 70-90k warnings per workday.

Thanks for the update.

Rafael


> Am 10.07.2011 12:58, schrieb Rafael J. Wysocki:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36182
> > Subject		: Erroneous package power limit notification since kernel 2.6.39
> > Submitter	: Olaf Freyer <aaron667-hi6Y0CQ0nG0@public.gmane.org>
> > Date		: 2011-05-22 13:01 (50 days old)
> > Message-ID	: <4DD9092A.4080507-hi6Y0CQ0nG0@public.gmane.org>
> > References	: http://marc.info/?l=linux-kernel&m=130606930631131&w=2
> >
> >
> >
> 
> 
> 

Re: [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Jeff Layton wrote:
> On Sun, 10 Jul 2011 14:58:54 +0300
> Pekka Enberg <penberg@kernel.org> wrote:
> 
> > On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.38 and 2.6.39.
> > >
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > > be listed and let the tracking team know (either way).
> > >
> > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=36952
> > > Subject         : [2.6.39] CIFS write failures where 2.6.38 works
> > > Submitter       : Helge Hafting <helge.hafting@hist.no>
> > > Date            : 2011-06-01 10:11 (40 days old)
> > > Message-ID      : <4DE6103E.6010100@hist.no>
> > > References      : http://marc.info/?l=linux-kernel&m=130692387613423&w=2
> > 
> > The last comment in Bugzilla states that Jeff was working on a patch.
> > Was it ever submitted to mainline and stable?
> > 
> >                                 Pekka
> 
> Yes, see commit 1190f6a067b in mainline. I also backported it for
> 2.6.39-stable and sent it to stable@kernel.org, but I haven't heard
> anything back on it yet (I'll resend if I don't hear anything in the
> next day or two).

Thanks, I've closed the bug.

Rafael

Re: [Bug #36952] [2.6.39] CIFS write failures where 2.6.38 works

[Rafael J. Wysocki]

On Sunday, July 10, 2011, Jeff Layton wrote:
> On Sun, 10 Jul 2011 14:58:54 +0300
> Pekka Enberg <penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> 
> > On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.38 and 2.6.39.
> > >
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > > be listed and let the tracking team know (either way).
> > >
> > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=36952
> > > Subject         : [2.6.39] CIFS write failures where 2.6.38 works
> > > Submitter       : Helge Hafting <helge.hafting-CND4fxrytsY@public.gmane.org>
> > > Date            : 2011-06-01 10:11 (40 days old)
> > > Message-ID      : <4DE6103E.6010100-CND4fxrytsY@public.gmane.org>
> > > References      : http://marc.info/?l=linux-kernel&m=130692387613423&w=2
> > 
> > The last comment in Bugzilla states that Jeff was working on a patch.
> > Was it ever submitted to mainline and stable?
> > 
> >                                 Pekka
> 
> Yes, see commit 1190f6a067b in mainline. I also backported it for
> 2.6.39-stable and sent it to stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, but I haven't heard
> anything back on it yet (I'll resend if I don't hear anything in the
> next day or two).

Thanks, I've closed the bug.

Rafael

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Keith Packard]

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On Sun, 10 Jul 2011 14:56:19 +0300, Pekka Enberg <penberg@kernel.org> wrote:

> There's no mention that the i915 developers know about this problem so
> I'm CC'ing Keith and Chris.

Thanks. I've added a comment to the bug:

First off, of course you are encouraged to re-test with 3.0-rc6 just to
make sure it hasn't changed in some way. I don't think anything has
changed enough to affect this, but it's always good to be sure.

I note a long sequence of patches that are supposed to help with the
U160:

448f53a1ede54eb854d036abf54573281412d650 drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
bcfbbce822d219eb587acaba8a6e062bbeae4761 Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"
a76150302d6e7ebc43e1a1ddaee7fd51db8da3b3 drm/i915: Add a module option to override the use of SSC

I'm not sure why a quirk wasn't added for this hardware; it's clearly
'non-standard' in some mystic way.

-- 
keith.packard@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Keith Packard]

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Sun, 10 Jul 2011 14:56:19 +0300, Pekka Enberg <penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:

> There's no mention that the i915 developers know about this problem so
> I'm CC'ing Keith and Chris.

Thanks. I've added a comment to the bug:

First off, of course you are encouraged to re-test with 3.0-rc6 just to
make sure it hasn't changed in some way. I don't think anything has
changed enough to affect this, but it's always good to be sure.

I note a long sequence of patches that are supposed to help with the
U160:

448f53a1ede54eb854d036abf54573281412d650 drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
bcfbbce822d219eb587acaba8a6e062bbeae4761 Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"
a76150302d6e7ebc43e1a1ddaee7fd51db8da3b3 drm/i915: Add a module option to override the use of SSC

I'm not sure why a quirk wasn't added for this hardware; it's clearly
'non-standard' in some mystic way.

-- 
keith.packard-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Steven Rostedt]

On Sun, 2011-07-10 at 14:53 +0300, Pekka Enberg wrote:
> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
> > Subject         : [Warning] 2.6.39.x latencytop
> > Submitter       : Andrew Watts <akwatts@ymail.com>
> > Date            : 2011-06-14 17:07 (27 days old)
> > Message-ID      : <80098.5633.qm@web111013.mail.gq1.yahoo.com>
> > References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2
> 
> This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
> tracing_enabled for tracing_on") that lets the user know about
> deprecated ABI. It's somewhat unfortunate that there's no mention in
> the changelog if everyone agreed on the deprecation or not...
> 
> That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
> I think this issue can be closed.

I deprecated it because I said I would for the last year ;)

The tracing_enabled never did what it was suppose to do. It was suppose
to be a "quick" way to disable tracing without fully disabling it. It
was suppose to try to turn things off to a low overhead but not fully
off without any overhead. The problem is that it never really worked
well. The only tracer that does anything different with it as suppose to
tracing_on, is the irqsoff tracers. They stop looking at max latencies
when you echo 0 into tracing_enabled. But that's it. Everything else,
it's just the same as echoing 0 into tracing_on. I think the irqsoff
tracers now even look at tracing_on if it should trace a max latency or
not, so tracing_enabled doesn't even help with that.

We can keep it around but I don't see any good reason for it besides not
having latency top give a warning.

Question: Why is latency top even touching this file?

-- Steve

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Steven Rostedt]

On Sun, 2011-07-10 at 14:53 +0300, Pekka Enberg wrote:
> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
> > Subject         : [Warning] 2.6.39.x latencytop
> > Submitter       : Andrew Watts <akwatts-DaQTI0RpDDMAvxtiuMwx3w@public.gmane.org>
> > Date            : 2011-06-14 17:07 (27 days old)
> > Message-ID      : <80098.5633.qm-tGSp4LqzbTn6X00i2u5GFvu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
> > References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2
> 
> This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
> tracing_enabled for tracing_on") that lets the user know about
> deprecated ABI. It's somewhat unfortunate that there's no mention in
> the changelog if everyone agreed on the deprecation or not...
> 
> That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
> I think this issue can be closed.

I deprecated it because I said I would for the last year ;)

The tracing_enabled never did what it was suppose to do. It was suppose
to be a "quick" way to disable tracing without fully disabling it. It
was suppose to try to turn things off to a low overhead but not fully
off without any overhead. The problem is that it never really worked
well. The only tracer that does anything different with it as suppose to
tracing_on, is the irqsoff tracers. They stop looking at max latencies
when you echo 0 into tracing_enabled. But that's it. Everything else,
it's just the same as echoing 0 into tracing_on. I think the irqsoff
tracers now even look at tracing_on if it should trace a max latency or
not, so tracing_enabled doesn't even help with that.

We can keep it around but I don't see any good reason for it besides not
having latency top give a warning.

Question: Why is latency top even touching this file?

-- Steve

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Pekka Enberg]

On Mon, Jul 11, 2011 at 12:25 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sun, 2011-07-10 at 14:53 +0300, Pekka Enberg wrote:
>> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>> > This message has been generated automatically as a part of a report
>> > of regressions introduced between 2.6.38 and 2.6.39.
>> >
>> > The following bug entry is on the current list of known regressions
>> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
>> > be listed and let the tracking team know (either way).
>> >
>> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
>> > Subject         : [Warning] 2.6.39.x latencytop
>> > Submitter       : Andrew Watts <akwatts@ymail.com>
>> > Date            : 2011-06-14 17:07 (27 days old)
>> > Message-ID      : <80098.5633.qm@web111013.mail.gq1.yahoo.com>
>> > References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2
>>
>> This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
>> tracing_enabled for tracing_on") that lets the user know about
>> deprecated ABI. It's somewhat unfortunate that there's no mention in
>> the changelog if everyone agreed on the deprecation or not...
>>
>> That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
>> I think this issue can be closed.
>
> I deprecated it because I said I would for the last year ;)
>
> The tracing_enabled never did what it was suppose to do. It was suppose
> to be a "quick" way to disable tracing without fully disabling it. It
> was suppose to try to turn things off to a low overhead but not fully
> off without any overhead. The problem is that it never really worked
> well. The only tracer that does anything different with it as suppose to
> tracing_on, is the irqsoff tracers. They stop looking at max latencies
> when you echo 0 into tracing_enabled. But that's it. Everything else,
> it's just the same as echoing 0 into tracing_on. I think the irqsoff
> tracers now even look at tracing_on if it should trace a max latency or
> not, so tracing_enabled doesn't even help with that.
>
> We can keep it around but I don't see any good reason for it besides not
> having latency top give a warning.

AFAICT, if you go ahead with the deprecation and actually remove the
file, you'll break latencytop fsync tracing.

On Mon, Jul 11, 2011 at 12:25 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> Question: Why is latency top even touching this file?

Looking at the sources, it seems to use it to enable fsync tracing. I
don't know the details so lets CC Arjan.

Re: [Bug #38132] [Warning] 2.6.39.x latencytop

[Pekka Enberg]

On Mon, Jul 11, 2011 at 12:25 AM, Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org> wrote:
> On Sun, 2011-07-10 at 14:53 +0300, Pekka Enberg wrote:
>> On Sun, Jul 10, 2011 at 1:58 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> > This message has been generated automatically as a part of a report
>> > of regressions introduced between 2.6.38 and 2.6.39.
>> >
>> > The following bug entry is on the current list of known regressions
>> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
>> > be listed and let the tracking team know (either way).
>> >
>> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=38132
>> > Subject         : [Warning] 2.6.39.x latencytop
>> > Submitter       : Andrew Watts <akwatts-DaQTI0RpDDMAvxtiuMwx3w@public.gmane.org>
>> > Date            : 2011-06-14 17:07 (27 days old)
>> > Message-ID      : <80098.5633.qm-tGSp4LqzbTn6X00i2u5GFvu2YVrzzGjV0BYs2hP7t38@public.gmane.orgm>
>> > References      : http://marc.info/?l=linux-kernel&m=130807128506490&w=2
>>
>> This is a WARN_ON added in commit 6752ab4a ("tracing: Deprecate
>> tracing_enabled for tracing_on") that lets the user know about
>> deprecated ABI. It's somewhat unfortunate that there's no mention in
>> the changelog if everyone agreed on the deprecation or not...
>>
>> That said, assuming the deprecation is OK (hi Steven, Frederic, Ingo!)
>> I think this issue can be closed.
>
> I deprecated it because I said I would for the last year ;)
>
> The tracing_enabled never did what it was suppose to do. It was suppose
> to be a "quick" way to disable tracing without fully disabling it. It
> was suppose to try to turn things off to a low overhead but not fully
> off without any overhead. The problem is that it never really worked
> well. The only tracer that does anything different with it as suppose to
> tracing_on, is the irqsoff tracers. They stop looking at max latencies
> when you echo 0 into tracing_enabled. But that's it. Everything else,
> it's just the same as echoing 0 into tracing_on. I think the irqsoff
> tracers now even look at tracing_on if it should trace a max latency or
> not, so tracing_enabled doesn't even help with that.
>
> We can keep it around but I don't see any good reason for it besides not
> having latency top give a warning.

AFAICT, if you go ahead with the deprecation and actually remove the
file, you'll break latencytop fsync tracing.

On Mon, Jul 11, 2011 at 12:25 AM, Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org> wrote:
> Question: Why is latency top even touching this file?

Looking at the sources, it seems to use it to enable fsync tracing. I
don't know the details so lets CC Arjan.

Re: [Bug #37752] Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller

[Martin]

On Sunday 10 July 2011 12:58:54 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.38 and 2.6.39.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37752
> Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine 
with
> 82915G/GV/910GL Integrated Graphics Controller Submitter	: Martin Rogge
> <marogge@onlinehome.de>
> Date		: 2011-06-17 13:02 (24 days old)

I have verified today that both 2.6.39.3 and 3.0-rc6 still show the problem. 
As before, 3.0-rc6 seems to have a longer uptime than 3.6.39.3. Both times I 
did not catch a proper kernel panic. The machine simply froze.

Martin

Re: [Bug #37752] Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine with 82915G/GV/910GL Integrated Graphics Controller

[Rafael J. Wysocki]

On Monday, July 11, 2011, Martin wrote:
> On Sunday 10 July 2011 12:58:54 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.38 and 2.6.39.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37752
> > Subject		: Kernel Panic in drm_vblank_put+0x13/0x50 on P4 HT machine 
> with
> > 82915G/GV/910GL Integrated Graphics Controller Submitter	: Martin Rogge
> > <marogge@onlinehome.de>
> > Date		: 2011-06-17 13:02 (24 days old)
> 
> I have verified today that both 2.6.39.3 and 3.0-rc6 still show the problem. 
> As before, 3.0-rc6 seems to have a longer uptime than 3.6.39.3. Both times I 
> did not catch a proper kernel panic. The machine simply froze.

Thanks for the update.

Rafael

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

Keith Packard <keithp@keithp.com> writes:

> On Sun, 10 Jul 2011 14:56:19 +0300, Pekka Enberg <penberg@kernel.org> wrote:
>
>> There's no mention that the i915 developers know about this problem so
>> I'm CC'ing Keith and Chris.
>
> Thanks. I've added a comment to the bug:
>
> First off, of course you are encouraged to re-test with 3.0-rc6 just to
> make sure it hasn't changed in some way. I don't think anything has
> changed enough to affect this, but it's always good to be sure.
>
> I note a long sequence of patches that are supposed to help with the
> U160:
>
> 448f53a1ede54eb854d036abf54573281412d650 drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
> bcfbbce822d219eb587acaba8a6e062bbeae4761 Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"
> a76150302d6e7ebc43e1a1ddaee7fd51db8da3b3 drm/i915: Add a module option to override the use of SSC
>
> I'm not sure why a quirk wasn't added for this hardware; it's clearly
> 'non-standard' in some mystic way.

On June 27th, I proposed that Robse perhaps could try the workaround
that was introduced with the latter commit: i915.lvds_use_ssc=0.

It works well on my hardware and probably solves his problem as well,
but he did not respond...

Dirk

[1] https://lkml.org/lkml/2011/6/27/45

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

Keith Packard <keithp-aN4HjG94KOLQT0dZR+AlfA@public.gmane.org> writes:

> On Sun, 10 Jul 2011 14:56:19 +0300, Pekka Enberg <penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>
>> There's no mention that the i915 developers know about this problem so
>> I'm CC'ing Keith and Chris.
>
> Thanks. I've added a comment to the bug:
>
> First off, of course you are encouraged to re-test with 3.0-rc6 just to
> make sure it hasn't changed in some way. I don't think anything has
> changed enough to affect this, but it's always good to be sure.
>
> I note a long sequence of patches that are supposed to help with the
> U160:
>
> 448f53a1ede54eb854d036abf54573281412d650 drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
> bcfbbce822d219eb587acaba8a6e062bbeae4761 Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"
> a76150302d6e7ebc43e1a1ddaee7fd51db8da3b3 drm/i915: Add a module option to override the use of SSC
>
> I'm not sure why a quirk wasn't added for this hardware; it's clearly
> 'non-standard' in some mystic way.

On June 27th, I proposed that Robse perhaps could try the workaround
that was introduced with the latter commit: i915.lvds_use_ssc=0.

It works well on my hardware and probably solves his problem as well,
but he did not respond...

Dirk

[1] https://lkml.org/lkml/2011/6/27/45

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de> writes:

> Keith Packard <keithp@keithp.com> writes:
>
>> On Sun, 10 Jul 2011 14:56:19 +0300, Pekka Enberg <penberg@kernel.org> wrote:
>>
>>> There's no mention that the i915 developers know about this problem so
>>> I'm CC'ing Keith and Chris.
>>
>> Thanks. I've added a comment to the bug:
>>
>> First off, of course you are encouraged to re-test with 3.0-rc6 just to
>> make sure it hasn't changed in some way. I don't think anything has
>> changed enough to affect this, but it's always good to be sure.
>>
>> I note a long sequence of patches that are supposed to help with the
>> U160:
>>
>> 448f53a1ede54eb854d036abf54573281412d650 drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
>> bcfbbce822d219eb587acaba8a6e062bbeae4761 Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"
>> a76150302d6e7ebc43e1a1ddaee7fd51db8da3b3 drm/i915: Add a module option to override the use of SSC
>>
>> I'm not sure why a quirk wasn't added for this hardware; it's clearly
>> 'non-standard' in some mystic way.
>
> On June 27th, I proposed that Robse perhaps could try the workaround
> that was introduced with the latter commit: i915.lvds_use_ssc=0.
>
> It works well on my hardware and probably solves his problem as well,
> but he did not respond...

I'm sorry for the noise, I did not check new comments in the bug report
where Robse noted that the workaround works for him.  I'm not sure if
that means the bug can be closed.

Sorry again,

Dirk

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

Dirk Gouders <gouders-UkMx63StcVObyvKg4uJg4nF3/sHOsa9/WV23jfQ1LcY@public.gmane.org> writes:

> Keith Packard <keithp-aN4HjG94KOLQT0dZR+AlfA@public.gmane.org> writes:
>
>> On Sun, 10 Jul 2011 14:56:19 +0300, Pekka Enberg <penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>>
>>> There's no mention that the i915 developers know about this problem so
>>> I'm CC'ing Keith and Chris.
>>
>> Thanks. I've added a comment to the bug:
>>
>> First off, of course you are encouraged to re-test with 3.0-rc6 just to
>> make sure it hasn't changed in some way. I don't think anything has
>> changed enough to affect this, but it's always good to be sure.
>>
>> I note a long sequence of patches that are supposed to help with the
>> U160:
>>
>> 448f53a1ede54eb854d036abf54573281412d650 drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks
>> bcfbbce822d219eb587acaba8a6e062bbeae4761 Revert "drm/i915/bios: Reverse order of 100/120 Mhz SSC clocks"
>> a76150302d6e7ebc43e1a1ddaee7fd51db8da3b3 drm/i915: Add a module option to override the use of SSC
>>
>> I'm not sure why a quirk wasn't added for this hardware; it's clearly
>> 'non-standard' in some mystic way.
>
> On June 27th, I proposed that Robse perhaps could try the workaround
> that was introduced with the latter commit: i915.lvds_use_ssc=0.
>
> It works well on my hardware and probably solves his problem as well,
> but he did not respond...

I'm sorry for the noise, I did not check new comments in the bug report
where Robse noted that the workaround works for him.  I'm not sure if
that means the bug can be closed.

Sorry again,

Dirk

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Keith Packard]

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

On Tue, 12 Jul 2011 10:35:13 +0200, Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de> wrote:

> I'm sorry for the noise, I did not check new comments in the bug report
> where Robse noted that the workaround works for him.  I'm not sure if
> that means the bug can be closed.

A kernel commandline workaround isn't ideal; we should at least provide
a quirk that does this automatically for this hardware. Can we get the
PCI information for the graphics device on this hardware (lspci -v -n)?

-- 
keith.packard@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Keith Packard]

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

On Tue, 12 Jul 2011 10:35:13 +0200, Dirk Gouders <gouders-UkMx63StcVObyvKg4uJg4mZHpeb/A1Y/@public.gmane.orgsenkirchen.de> wrote:

> I'm sorry for the noise, I did not check new comments in the bug report
> where Robse noted that the workaround works for him.  I'm not sure if
> that means the bug can be closed.

A kernel commandline workaround isn't ideal; we should at least provide
a quirk that does this automatically for this hardware. Can we get the
PCI information for the graphics device on this hardware (lspci -v -n)?

-- 
keith.packard-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

Keith Packard <keithp@keithp.com> writes:

> On Tue, 12 Jul 2011 10:35:13 +0200, Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de> wrote:
>
>> I'm sorry for the noise, I did not check new comments in the bug report
>> where Robse noted that the workaround works for him.  I'm not sure if
>> that means the bug can be closed.
>
> A kernel commandline workaround isn't ideal; we should at least provide
> a quirk that does this automatically for this hardware. Can we get the
> PCI information for the graphics device on this hardware (lspci -v -n)?

Of course.  Probably, some of the information in the bug report at
freedesktop.org[1] is also useful.

Dirk

[1] https://bugs.freedesktop.org/show_bug.cgi?id=31596

------------------------------------------------------------------------
00:00.0 0600: 8086:0044 (rev 02)
	Subsystem: 17aa:391e
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: agpgart-intel

00:02.0 0300: 8086:0046 (rev 02) (prog-if 00 [VGA controller])
	Subsystem: 17aa:3920
	Flags: bus master, fast devsel, latency 0, IRQ 41
	Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 1800 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915

00:16.0 0780: 8086:3b64 (rev 06)
	Subsystem: 17aa:38a5
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at f0804000 (64-bit, non-prefetchable) [size=16]
	Capabilities: [50] Power Management version 3
	Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+

00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
	Subsystem: 17aa:38aa
	Flags: bus master, medium devsel, latency 0, IRQ 16
	Memory at f0806000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd

00:1b.0 0403: 8086:3b56 (rev 05)
	Subsystem: 17aa:38af
	Flags: bus master, fast devsel, latency 0, IRQ 42
	Memory at f0800000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel

00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f0400000-f04fffff
	Prefetchable memory behind bridge: 000000007c200000-000000007c3fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:38b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1c.1 0604: 8086:3b44 (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: f0500000-f05fffff
	Prefetchable memory behind bridge: 000000007c000000-000000007c1fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:38b1
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
	Subsystem: 17aa:38b8
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f0807000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd

00:1e.0 0604: 8086:2448 (rev a5) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0f, subordinate=0f, sec-latency=0
	Capabilities: [50] Subsystem: 17aa:383f

00:1f.0 0601: 8086:3b09 (rev 05)
	Subsystem: 17aa:38be
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:1f.2 0106: 8086:3b29 (rev 05) (prog-if 01 [AHCI 1.0])
	Subsystem: 17aa:38c1
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 40
	I/O ports at 1818 [size=8]
	I/O ports at 180c [size=4]
	I/O ports at 1810 [size=8]
	I/O ports at 1808 [size=4]
	I/O ports at 1820 [size=32]
	Memory at f0808000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Power Management version 3
	Capabilities: [a8] SATA HBA v1.0
	Capabilities: [b0] PCI Advanced Features
	Kernel driver in use: ahci

00:1f.3 0c05: 8086:3b30 (rev 05)
	Subsystem: 17aa:38bf
	Flags: medium devsel, IRQ 18
	Memory at f0809000 (64-bit, non-prefetchable) [size=256]
	I/O ports at 1840 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801

00:1f.6 1180: 8086:3b32 (rev 05)
	Subsystem: 17aa:38c0
	Flags: fast devsel, IRQ 10
	Memory at f080a000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-

03:00.0 0200: 1969:1063 (rev c0)
	Subsystem: 17aa:38a3
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0400000 (64-bit, non-prefetchable) [size=256K]
	I/O ports at 2000 [size=128]
	Capabilities: [40] Power Management version 3
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [58] Express Endpoint, MSI 00
	Capabilities: [6c] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [180] Device Serial Number ff-0a-37-ef-5c-ff-35-ff
	Kernel driver in use: atl1c
	Kernel modules: atl1c

04:00.0 0280: 14e4:4727 (rev 01)
	Subsystem: 14e4:0510
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at f0500000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-00-82-ff-ff-6e-00-26
	Capabilities: [16c] Power Budgeting <?>
	Kernel driver in use: wl
	Kernel modules: wl

ff:00.0 0600: 8086:2c62 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:00.1 0600: 8086:2d01 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.0 0600: 8086:2d10 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.1 0600: 8086:2d11 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.2 0600: 8086:2d12 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.3 0600: 8086:2d13 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

Keith Packard <keithp-aN4HjG94KOLQT0dZR+AlfA@public.gmane.org> writes:

> On Tue, 12 Jul 2011 10:35:13 +0200, Dirk Gouders <gouders-UkMx63StcVObyvKg4uJg4nF3/sHOsa9/WV23jfQ1LcY@public.gmane.org> wrote:
>
>> I'm sorry for the noise, I did not check new comments in the bug report
>> where Robse noted that the workaround works for him.  I'm not sure if
>> that means the bug can be closed.
>
> A kernel commandline workaround isn't ideal; we should at least provide
> a quirk that does this automatically for this hardware. Can we get the
> PCI information for the graphics device on this hardware (lspci -v -n)?

Of course.  Probably, some of the information in the bug report at
freedesktop.org[1] is also useful.

Dirk

[1] https://bugs.freedesktop.org/show_bug.cgi?id=31596

------------------------------------------------------------------------
00:00.0 0600: 8086:0044 (rev 02)
	Subsystem: 17aa:391e
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: agpgart-intel

00:02.0 0300: 8086:0046 (rev 02) (prog-if 00 [VGA controller])
	Subsystem: 17aa:3920
	Flags: bus master, fast devsel, latency 0, IRQ 41
	Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 1800 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915

00:16.0 0780: 8086:3b64 (rev 06)
	Subsystem: 17aa:38a5
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at f0804000 (64-bit, non-prefetchable) [size=16]
	Capabilities: [50] Power Management version 3
	Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+

00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
	Subsystem: 17aa:38aa
	Flags: bus master, medium devsel, latency 0, IRQ 16
	Memory at f0806000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd

00:1b.0 0403: 8086:3b56 (rev 05)
	Subsystem: 17aa:38af
	Flags: bus master, fast devsel, latency 0, IRQ 42
	Memory at f0800000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel

00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f0400000-f04fffff
	Prefetchable memory behind bridge: 000000007c200000-000000007c3fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:38b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1c.1 0604: 8086:3b44 (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: f0500000-f05fffff
	Prefetchable memory behind bridge: 000000007c000000-000000007c1fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:38b1
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
	Subsystem: 17aa:38b8
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f0807000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd

00:1e.0 0604: 8086:2448 (rev a5) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0f, subordinate=0f, sec-latency=0
	Capabilities: [50] Subsystem: 17aa:383f

00:1f.0 0601: 8086:3b09 (rev 05)
	Subsystem: 17aa:38be
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:1f.2 0106: 8086:3b29 (rev 05) (prog-if 01 [AHCI 1.0])
	Subsystem: 17aa:38c1
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 40
	I/O ports at 1818 [size=8]
	I/O ports at 180c [size=4]
	I/O ports at 1810 [size=8]
	I/O ports at 1808 [size=4]
	I/O ports at 1820 [size=32]
	Memory at f0808000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Power Management version 3
	Capabilities: [a8] SATA HBA v1.0
	Capabilities: [b0] PCI Advanced Features
	Kernel driver in use: ahci

00:1f.3 0c05: 8086:3b30 (rev 05)
	Subsystem: 17aa:38bf
	Flags: medium devsel, IRQ 18
	Memory at f0809000 (64-bit, non-prefetchable) [size=256]
	I/O ports at 1840 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801

00:1f.6 1180: 8086:3b32 (rev 05)
	Subsystem: 17aa:38c0
	Flags: fast devsel, IRQ 10
	Memory at f080a000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-

03:00.0 0200: 1969:1063 (rev c0)
	Subsystem: 17aa:38a3
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0400000 (64-bit, non-prefetchable) [size=256K]
	I/O ports at 2000 [size=128]
	Capabilities: [40] Power Management version 3
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [58] Express Endpoint, MSI 00
	Capabilities: [6c] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [180] Device Serial Number ff-0a-37-ef-5c-ff-35-ff
	Kernel driver in use: atl1c
	Kernel modules: atl1c

04:00.0 0280: 14e4:4727 (rev 01)
	Subsystem: 14e4:0510
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at f0500000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-00-82-ff-ff-6e-00-26
	Capabilities: [16c] Power Budgeting <?>
	Kernel driver in use: wl
	Kernel modules: wl

ff:00.0 0600: 8086:2c62 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:00.1 0600: 8086:2d01 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.0 0600: 8086:2d10 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.1 0600: 8086:2d11 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.2 0600: 8086:2d12 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

ff:02.3 0600: 8086:2d13 (rev 02)
	Subsystem: 17aa:392b
	Flags: bus master, fast devsel, latency 0

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
> Subject		: Lenovo U160 (i915 black screen)
> Submitter	: Robse <rob-se@live.de>
> Date		: 2011-06-14 15:17 (13 days old)

This sounds like a problem, I was discussing with Jesse Barnes, some
days ago[1].  For me, the usage of the kernel parameter
'i915.lvds_use_ssc=0' serves as a useful workaround.

Perhaps, Robse will try that option and document it in the Bug-Entry if
it also works for him.

Dirk

[1] https://lkml.org/lkml/2011/5/31/387

Re: [Bug #37472] Lenovo U160 (i915 black screen)

[Dirk Gouders]

> The following bug entry is on the current list of known regressions
> introduced between 2.6.38 and 2.6.39.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
> Subject		: Lenovo U160 (i915 black screen)
> Submitter	: Robse <rob-se-Dz115AEZgoU@public.gmane.org>
> Date		: 2011-06-14 15:17 (13 days old)

This sounds like a problem, I was discussing with Jesse Barnes, some
days ago[1].  For me, the usage of the kernel parameter
'i915.lvds_use_ssc=0' serves as a useful workaround.

Perhaps, Robse will try that option and document it in the Bug-Entry if
it also works for him.

Dirk

[1] https://lkml.org/lkml/2011/5/31/387

[Bug #37472] Lenovo U160 (i915 black screen)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
Subject		: Lenovo U160 (i915 black screen)
Submitter	: Robse <rob-se@live.de>
Date		: 2011-06-14 15:17 (13 days old)

[Bug #37472] Lenovo U160 (i915 black screen)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38 and 2.6.39.

The following bug entry is on the current list of known regressions
introduced between 2.6.38 and 2.6.39.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=37472
Subject		: Lenovo U160 (i915 black screen)
Submitter	: Robse <rob-se-Dz115AEZgoU@public.gmane.org>
Date		: 2011-06-14 15:17 (13 days old)