2.6.34-rc5: Reported regressions from 2.6.33

2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.33,
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 regressions from 2.6.33, 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
  ----------------------------------------
  2010-04-20       64       35          34
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15812
Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
Submitter	:  <adi-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
Date		: 2010-04-19 21:28 (1 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-15 21:02 (5 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15796
Subject		: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0
Submitter	: Éric Piel <Eric.Piel-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
Date		: 2010-04-13 21:54 (7 days old)
First-Bad-Commit: http://kernel.org/git/linus/7b3a177b0d4f92b3431b8dca777313a07533a710
Message-ID	: <4BC4E812.6050602-VkQ1JFuSMpfAbQlEx87xDw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127119569009790&w=2
Handled-By	: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15795
Subject		: 2.6.34-rc4 : OOPS in unmap_vma
Submitter	: Parag Warudkar <parag.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-14 (6 days old)
Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15790
Subject		: Meta-Bug: Regressions
Submitter	: Florian Mickler <fmickler-Mmb7MZpHnFY@public.gmane.org>
Date		: 2010-04-15 18:21 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15788
Subject		: external usb sound card doesn't work after resume
Submitter	: François Valenduc <francois.valenduc-bmtTS95sd5BUM80lpFwj4w@public.gmane.org>
Date		: 2010-04-15 10:16 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15774
Subject		: 2.6.34-rc3: eth0 (8139too): transmit queue 0 timed out
Submitter	: Németh Márton <nm127-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
Date		: 2010-04-10 12:33 (10 days old)
Message-ID	: <4BC07022.6000708-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127090287021976&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15768
Subject		: Incorrectly calculated free blocks result in ENOSPC from writepage
Submitter	: Dmitry Monakhov <dmonakhov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Date		: 2010-04-12 11:24 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15744
Subject		: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)
Submitter	: Andy Isaacson <adi-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
Date		: 2010-04-06 22:54 (14 days old)
Message-ID	: <<4BC51312.6080302-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org></desc>>
References	: http://marc.info/?l=linux-kernel&m=127059449031511&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15730
Subject		: Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)
Submitter	: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Date		: 2010-04-02 17:59 (18 days old)
Message-ID	: <20100402175937.GA19690-f9CnO7I+Q6zU6FkGJEIX5A@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127023173329741&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15729
Subject		: BUG: physmap modprobe & rmmod
Submitter	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-04-02 20:40 (18 days old)
Message-ID	: <20100402134058.c4682716.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15719
Subject		: virtio_net causing kernel BUG when running under VirtualBox
Submitter	: Thomas Müller <thomas-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
Date		: 2010-03-27 14:32 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
Message-ID	: <4BAE1707.2050803-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
Handled-By	: Shirley Ma <mashirle-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-14 20:14 (37 days old)
Message-ID	: <20100314201434.GE22059-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-25 8:40 (26 days old)
First-Bad-Commit: http://kernel.org/git/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel-c8rhgrCDLIED0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
		  Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-04-01 6:06 (19 days old)
Message-ID	: <20100401060624.GA1329-+ZI9xUNit7I@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15711
Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
Submitter	: Heinz Diehl <htd-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
Date		: 2010-04-01 17:52 (19 days old)
Message-ID	: <20100401175225.GA6581-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-31 10:21 (20 days old)
Message-ID	: <<20100331102142.GA3294-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15698
Subject		: Freeze on power-off / suspend to ram
Submitter	: arond <hector1987-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-05 13:53 (15 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Date		: 2010-03-28 11:31 (23 days old)
Message-ID	: <1269775909.5301.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15672
Subject		: KVM bug, git bisected
Submitter	: Kent Overstreet <kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-27 12:43 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
Message-ID	: <4BADFD74.8060904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126969385121711&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
Date		: 2010-03-27 16:11 (24 days old)
Message-ID	: <20100327161104.GA12043-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-08 1:26 (43 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58-JsoAwUIsXounXO2b/Sh1tA@public.gmane.orgom>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
Subject		: start_kernel(): bug: interrupts were enabled early
Submitter	: Rabin Vincent <rabin-66gdRtMMWGc@public.gmane.org>
Date		: 2010-03-25 19:53 (26 days old)
First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
Message-ID	: <20100325194100.GA2364@debian>
References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci-x0m+Mc+nT7uljOmnV8AmnkElSqmLX1BE@public.gmane.org>
Date		: 2010-04-01 01:09 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15661
Subject		: PROBLEM: crash on halt with 2.6.34-0.16.rc2.git0.fc14.x86_64
Submitter	: Jon Masters <jonathan-Zp4isUonpHBD60Wz+7aTrA@public.gmane.org>
Date		: 2010-03-26 15:29 (25 days old)
Message-ID	: <<1269617372.3779.234.camel@localhost>>
References	: http://marc.info/?l=linux-kernel&m=126961739803949&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-25 20:04 (26 days old)
Message-ID	: <201003252104.24965.maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15625
Subject		: BUG: 2.6.34-rc1, RIP is (null)
Submitter	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-03-18 22:22 (33 days old)
Message-ID	: <4BA2A7A9.4080503-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126895098217351&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15611
Subject		: Failure with the 2.6.34-rc1 kernel
Submitter	: Rupjyoti Sarmah <rsarmah-6mNVq6Owofk@public.gmane.org>
Date		: 2010-03-16 15:45 (35 days old)
Message-ID	: <AC311A8E81420D4EBC1F26E6479848FE065B7D3D-oUPhqDSr77q+n3Z1v9ZxkQ@public.gmane.org.amcc.com>
References	: http://marc.info/?l=linux-kernel&m=126875435718396&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-03-22 15:59 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org
Date		: 2010-03-15 13:39 (36 days old)
Message-ID	: <4B9E38AF.70309-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-14 7:58 (37 days old)
Message-ID	: <20100314075831.GA13457-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (38 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15553
Subject		: Screen backlight doesn't come back on after lid was closed (GM45)
Submitter	:  <bugs-fbdoOxCsnNob1SvskN2V4Q@public.gmane.org>
Date		: 2010-03-17 14:35 (34 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15551
Subject		: WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()
Submitter	: Alex Zhavnerchik <alex.vizor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-16 22:03 (35 days old)


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian-GANU6spQydw@public.gmane.org>
Date		: 2010-03-10 06:59 (41 days old)
Handled-By	: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11


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 from 2.6.33,
unresolved as well as resolved, at:

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

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

Thanks!

2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.33,
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 regressions from 2.6.33, 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
  ----------------------------------------
  2010-04-20       64       35          34
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15812
Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
Submitter	:  <adi@hexapodia.org>
Date		: 2010-04-19 21:28 (1 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2010-04-15 21:02 (5 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15796
Subject		: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0
Submitter	: Éric Piel <Eric.Piel@tremplin-utc.net>
Date		: 2010-04-13 21:54 (7 days old)
First-Bad-Commit: http://kernel.org/git/linus/7b3a177b0d4f92b3431b8dca777313a07533a710
Message-ID	: <4BC4E812.6050602@tremplin-utc.net>
References	: http://marc.info/?l=linux-kernel&m=127119569009790&w=2
Handled-By	: Takashi Iwai <tiwai@suse.de>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15795
Subject		: 2.6.34-rc4 : OOPS in unmap_vma
Submitter	: Parag Warudkar <parag.lkml@gmail.com>
Date		: 2010-04-14 (6 days old)
Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15790
Subject		: Meta-Bug: Regressions
Submitter	: Florian Mickler <fmickler@gmx.de>
Date		: 2010-04-15 18:21 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15788
Subject		: external usb sound card doesn't work after resume
Submitter	: François Valenduc <francois.valenduc@tvcablenet.be>
Date		: 2010-04-15 10:16 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15774
Subject		: 2.6.34-rc3: eth0 (8139too): transmit queue 0 timed out
Submitter	: Németh Márton <nm127@freemail.hu>
Date		: 2010-04-10 12:33 (10 days old)
Message-ID	: <4BC07022.6000708@freemail.hu>
References	: http://marc.info/?l=linux-kernel&m=127090287021976&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15768
Subject		: Incorrectly calculated free blocks result in ENOSPC from writepage
Submitter	: Dmitry Monakhov <dmonakhov@openvz.org>
Date		: 2010-04-12 11:24 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15744
Subject		: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)
Submitter	: Andy Isaacson <adi@hexapodia.org>
Date		: 2010-04-06 22:54 (14 days old)
Message-ID	: <<4BC51312.6080302@oracle.com></desc>>
References	: http://marc.info/?l=linux-kernel&m=127059449031511&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15730
Subject		: Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)
Submitter	: Borislav Petkov <bp@alien8.de>
Date		: 2010-04-02 17:59 (18 days old)
Message-ID	: <20100402175937.GA19690@liondog.tnic>
References	: http://marc.info/?l=linux-kernel&m=127023173329741&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15729
Subject		: BUG: physmap modprobe & rmmod
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-04-02 20:40 (18 days old)
Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15719
Subject		: virtio_net causing kernel BUG when running under VirtualBox
Submitter	: Thomas Müller <thomas@mathtm.de>
Date		: 2010-03-27 14:32 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
Message-ID	: <4BAE1707.2050803@mathtm.de>
References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
Handled-By	: Shirley Ma <mashirle@us.ibm.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 20:14 (37 days old)
Message-ID	: <20100314201434.GE22059@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi@intel.com>
Date		: 2010-03-25 8:40 (26 days old)
First-Bad-Commit: http://kernel.org/git/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel@alexs-hp.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl@linux-foundation.org>
		  Pekka Enberg <penberg@cs.helsinki.fi>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-04-01 6:06 (19 days old)
Message-ID	: <20100401060624.GA1329@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15711
Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
Submitter	: Heinz Diehl <htd@fancy-poultry.org>
Date		: 2010-04-01 17:52 (19 days old)
Message-ID	: <20100401175225.GA6581@fancy-poultry.org>
References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date		: 2010-03-31 10:21 (20 days old)
Message-ID	: <<20100331102142.GA3294@swordfish.minsk.epam.com>>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15698
Subject		: Freeze on power-off / suspend to ram
Submitter	: arond <hector1987@gmail.com>
Date		: 2010-04-05 13:53 (15 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-03-28 11:31 (23 days old)
Message-ID	: <1269775909.5301.4.camel@localhost.localdomain>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15672
Subject		: KVM bug, git bisected
Submitter	: Kent Overstreet <kent.overstreet@gmail.com>
Date		: 2010-03-27 12:43 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
Message-ID	: <4BADFD74.8060904@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126969385121711&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2010-03-27 16:11 (24 days old)
Message-ID	: <20100327161104.GA12043@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-03-08 1:26 (43 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
Subject		: start_kernel(): bug: interrupts were enabled early
Submitter	: Rabin Vincent <rabin@rab.in>
Date		: 2010-03-25 19:53 (26 days old)
First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
Message-ID	: <20100325194100.GA2364@debian>
References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date		: 2010-04-01 01:09 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15661
Subject		: PROBLEM: crash on halt with 2.6.34-0.16.rc2.git0.fc14.x86_64
Submitter	: Jon Masters <jonathan@jonmasters.org>
Date		: 2010-03-26 15:29 (25 days old)
Message-ID	: <<1269617372.3779.234.camel@localhost>>
References	: http://marc.info/?l=linux-kernel&m=126961739803949&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2010-03-25 20:04 (26 days old)
Message-ID	: <201003252104.24965.maciej.rutecki@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15625
Subject		: BUG: 2.6.34-rc1, RIP is (null)
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-03-18 22:22 (33 days old)
Message-ID	: <4BA2A7A9.4080503@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=126895098217351&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15611
Subject		: Failure with the 2.6.34-rc1 kernel
Submitter	: Rupjyoti Sarmah <rsarmah@amcc.com>
Date		: 2010-03-16 15:45 (35 days old)
Message-ID	: <AC311A8E81420D4EBC1F26E6479848FE065B7D3D@SDCEXCHANGE01.ad.amcc.com>
References	: http://marc.info/?l=linux-kernel&m=126875435718396&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel@oracle.com>
Date		: 2010-03-22 15:59 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev@fami-braun.de
Date		: 2010-03-15 13:39 (36 days old)
Message-ID	: <4B9E38AF.70309@fami-braun.de>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 7:58 (37 days old)
Message-ID	: <20100314075831.GA13457@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (38 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15553
Subject		: Screen backlight doesn't come back on after lid was closed (GM45)
Submitter	:  <bugs@kaijauch.de>
Date		: 2010-03-17 14:35 (34 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15551
Subject		: WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()
Submitter	: Alex Zhavnerchik <alex.vizor@gmail.com>
Date		: 2010-03-16 22:03 (35 days old)


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2010-03-10 06:59 (41 days old)
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11


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 from 2.6.33,
unresolved as well as resolved, at:

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

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

Thanks!

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Andrew Morton]

On Tue, 20 Apr 2010 05:15:57 +0200 (CEST) "Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15812
> Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
> Submitter	:  <adi@hexapodia.org>
> Date		: 2010-04-19 21:28 (1 days old)

I merged hch's fix for this twelve seconds ago.

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Andrew Morton]

On Tue, 20 Apr 2010 05:15:57 +0200 (CEST) "Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15812
> Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
> Submitter	:  <adi@hexapodia.org>
> Date		: 2010-04-19 21:28 (1 days old)

I merged hch's fix for this twelve seconds ago.

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Andrew Morton wrote:
> On Tue, 20 Apr 2010 05:15:57 +0200 (CEST) "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15812
> > Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
> > Submitter	:  <adi@hexapodia.org>
> > Date		: 2010-04-19 21:28 (1 days old)
> 
> I merged hch's fix for this twelve seconds ago.

I updated the entry.

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Andrew Morton wrote:
> On Tue, 20 Apr 2010 05:15:57 +0200 (CEST) "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15812
> > Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
> > Submitter	:  <adi@hexapodia.org>
> > Date		: 2010-04-19 21:28 (1 days old)
> 
> I merged hch's fix for this twelve seconds ago.

I updated the entry.

[Bug #15505] No more b43 wireless interface since 2.6.34-rc1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian-GANU6spQydw@public.gmane.org>
Date		: 2010-03-10 06:59 (41 days old)
Handled-By	: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11

[Bug #15505] No more b43 wireless interface since 2.6.34-rc1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2010-03-10 06:59 (41 days old)
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (38 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (38 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Tue, 20 Apr 2010 at 05:19, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> Date		: 2010-03-13 23:53 (38 days old)
> Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Yes, unless something in this area has changed from -rc4 to -rc5, this is 
still printed during boot:


device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
name 'pulses/rev'
------------[ cut here ]------------
Badness at fs/proc/generic.c:317
NIP: c00e14b8 LR: c00e14b8 CTR: c01fc2c0
REGS: c045bdc0 TRAP: 0700   Not tainted  (2.6.34-rc4)
MSR: 00029032 <EE,ME,CE,IR,DR>  CR: 22000022  XER: 20000000
TASK = c043b410[0] 'swapper' THREAD: c045a000
GPR00: c00e14b8 c045be70 c043b410 00000024 000012ff ffffffff ffffffff 00000000 
GPR08: ef808320 c0458670 00000000 000012ff 42000028 00000000 00cb3ccc 00cb39b8 
GPR16: 00cd682c 00cb3ca8 00cb38c8 00cb39ac 00240e18 00240e20 00cb3954 00240e24 
GPR24: 00000000 0049b000 c045be98 c045bec8 c0da0a42 c0da0a42 00000006 00000000 
NIP [c00e14b8] __xlate_proc_name+0xd0/0xf8
LR [c00e14b8] __xlate_proc_name+0xd0/0xf8
Call Trace:
[c045be70] [c00e14b8] __xlate_proc_name+0xd0/0xf8 (unreliable)
[c045be90] [c00e1a2c] __proc_create+0x60/0xf0
[c045bec0] [c00e2194] proc_create_data+0x54/0xc4
[c045bee0] [c00e6310] __proc_device_tree_add_prop+0x64/0xd4
[c045bf00] [c00e64b4] proc_device_tree_add_node+0x134/0x164
[c045bf20] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf40] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf60] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf80] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bfa0] [c0421c30] proc_device_tree_init+0x4c/0x78
[c045bfb0] [c0421698] proc_root_init+0xcc/0xf0
[c045bfc0] [c040e798] start_kernel+0x230/0x284
[c045bff0] [00003444] 0x3444
Instruction dump:
93ba0000 38600000 93fb0000 80010024 bb410008 38210020 7c0803a6 4e800020 
3c60c03c 7f84e378 386300a8 48273a45 <0fe00000> 80010024 3860fffe bb410008 


-- 
BOFH excuse #37:

heavy gravity fluctuation, move computer to floor rapidly

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Tue, 20 Apr 2010 at 05:19, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (38 days old)
> Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Yes, unless something in this area has changed from -rc4 to -rc5, this is 
still printed during boot:


device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
name 'pulses/rev'
------------[ cut here ]------------
Badness at fs/proc/generic.c:317
NIP: c00e14b8 LR: c00e14b8 CTR: c01fc2c0
REGS: c045bdc0 TRAP: 0700   Not tainted  (2.6.34-rc4)
MSR: 00029032 <EE,ME,CE,IR,DR>  CR: 22000022  XER: 20000000
TASK = c043b410[0] 'swapper' THREAD: c045a000
GPR00: c00e14b8 c045be70 c043b410 00000024 000012ff ffffffff ffffffff 00000000 
GPR08: ef808320 c0458670 00000000 000012ff 42000028 00000000 00cb3ccc 00cb39b8 
GPR16: 00cd682c 00cb3ca8 00cb38c8 00cb39ac 00240e18 00240e20 00cb3954 00240e24 
GPR24: 00000000 0049b000 c045be98 c045bec8 c0da0a42 c0da0a42 00000006 00000000 
NIP [c00e14b8] __xlate_proc_name+0xd0/0xf8
LR [c00e14b8] __xlate_proc_name+0xd0/0xf8
Call Trace:
[c045be70] [c00e14b8] __xlate_proc_name+0xd0/0xf8 (unreliable)
[c045be90] [c00e1a2c] __proc_create+0x60/0xf0
[c045bec0] [c00e2194] proc_create_data+0x54/0xc4
[c045bee0] [c00e6310] __proc_device_tree_add_prop+0x64/0xd4
[c045bf00] [c00e64b4] proc_device_tree_add_node+0x134/0x164
[c045bf20] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf40] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf60] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf80] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bfa0] [c0421c30] proc_device_tree_init+0x4c/0x78
[c045bfb0] [c0421698] proc_root_init+0xcc/0xf0
[c045bfc0] [c040e798] start_kernel+0x230/0x284
[c045bff0] [00003444] 0x3444
Instruction dump:
93ba0000 38600000 93fb0000 80010024 bb410008 38210020 7c0803a6 4e800020 
3c60c03c 7f84e378 386300a8 48273a45 <0fe00000> 80010024 3860fffe bb410008 


-- 
BOFH excuse #37:

heavy gravity fluctuation, move computer to floor rapidly

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Tue, 20 Apr 2010 at 05:19, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (38 days old)
> Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Yes, unless something in this area has changed from -rc4 to -rc5, this is 
still printed during boot:


device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
name 'pulses/rev'
------------[ cut here ]------------
Badness at fs/proc/generic.c:317
NIP: c00e14b8 LR: c00e14b8 CTR: c01fc2c0
REGS: c045bdc0 TRAP: 0700   Not tainted  (2.6.34-rc4)
MSR: 00029032 <EE,ME,CE,IR,DR>  CR: 22000022  XER: 20000000
TASK = c043b410[0] 'swapper' THREAD: c045a000
GPR00: c00e14b8 c045be70 c043b410 00000024 000012ff ffffffff ffffffff 00000000 
GPR08: ef808320 c0458670 00000000 000012ff 42000028 00000000 00cb3ccc 00cb39b8 
GPR16: 00cd682c 00cb3ca8 00cb38c8 00cb39ac 00240e18 00240e20 00cb3954 00240e24 
GPR24: 00000000 0049b000 c045be98 c045bec8 c0da0a42 c0da0a42 00000006 00000000 
NIP [c00e14b8] __xlate_proc_name+0xd0/0xf8
LR [c00e14b8] __xlate_proc_name+0xd0/0xf8
Call Trace:
[c045be70] [c00e14b8] __xlate_proc_name+0xd0/0xf8 (unreliable)
[c045be90] [c00e1a2c] __proc_create+0x60/0xf0
[c045bec0] [c00e2194] proc_create_data+0x54/0xc4
[c045bee0] [c00e6310] __proc_device_tree_add_prop+0x64/0xd4
[c045bf00] [c00e64b4] proc_device_tree_add_node+0x134/0x164
[c045bf20] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf40] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf60] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bf80] [c00e6434] proc_device_tree_add_node+0xb4/0x164
[c045bfa0] [c0421c30] proc_device_tree_init+0x4c/0x78
[c045bfb0] [c0421698] proc_root_init+0xcc/0xf0
[c045bfc0] [c040e798] start_kernel+0x230/0x284
[c045bff0] [00003444] 0x3444
Instruction dump:
93ba0000 38600000 93fb0000 80010024 bb410008 38210020 7c0803a6 4e800020 
3c60c03c 7f84e378 386300a8 48273a45 <0fe00000> 80010024 3860fffe bb410008 


-- 
BOFH excuse #37:

heavy gravity fluctuation, move computer to floor rapidly

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> On Tue, 20 Apr 2010 at 05:19, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> > Date		: 2010-03-13 23:53 (38 days old)
> > Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> Yes, unless something in this area has changed from -rc4 to -rc5, this is 
> still printed during boot:
> 
> 
> device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
> name 'pulses/rev'
> ------------[ cut here ]------------

Don't cut here, sigh.

> Badness at fs/proc/generic.c:317

Try this 100% unbuilt, 100% untested patch.

cheers


diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index f8650dc..9502b48 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -175,6 +175,24 @@ retry:
        return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+       char *p, *fixed_name;
+
+       fixed_name = kstrdup(name);
+       if (!fixed_name) {
+               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+                               "name \"%s\"\n", name);
+               return name;
+       }
+
+       p = fixed_name;
+       while ((p = strstr(p, "/")))
+               *p++ = '_';
+
+       return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -211,6 +229,9 @@ void proc_device_tree_add_node(struct device_node *np,
                if (duplicate_name(de, p))
                        p = fixup_name(np, de, p);
 
+               if (strstr(p, "/"))
+                       p = unslash_name(p);
+
                ent = __proc_device_tree_add_prop(de, pp, p);
                if (ent == NULL)
                        break;

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> On Tue, 20 Apr 2010 at 05:19, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists@nerdbynature.de>
> > Date		: 2010-03-13 23:53 (38 days old)
> > Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> Yes, unless something in this area has changed from -rc4 to -rc5, this is 
> still printed during boot:
> 
> 
> device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
> name 'pulses/rev'
> ------------[ cut here ]------------

Don't cut here, sigh.

> Badness at fs/proc/generic.c:317

Try this 100% unbuilt, 100% untested patch.

cheers


diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index f8650dc..9502b48 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -175,6 +175,24 @@ retry:
        return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+       char *p, *fixed_name;
+
+       fixed_name = kstrdup(name);
+       if (!fixed_name) {
+               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+                               "name \"%s\"\n", name);
+               return name;
+       }
+
+       p = fixed_name;
+       while ((p = strstr(p, "/")))
+               *p++ = '_';
+
+       return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -211,6 +229,9 @@ void proc_device_tree_add_node(struct device_node *np,
                if (duplicate_name(de, p))
                        p = fixup_name(np, de, p);
 
+               if (strstr(p, "/"))
+                       p = unslash_name(p);
+
                ent = __proc_device_tree_add_prop(de, pp, p);
                if (ent == NULL)
                        break;

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> On Tue, 20 Apr 2010 at 05:19, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists@nerdbynature.de>
> > Date		: 2010-03-13 23:53 (38 days old)
> > Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> Yes, unless something in this area has changed from -rc4 to -rc5, this is 
> still printed during boot:
> 
> 
> device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
> name 'pulses/rev'
> ------------[ cut here ]------------

Don't cut here, sigh.

> Badness at fs/proc/generic.c:317

Try this 100% unbuilt, 100% untested patch.

cheers


diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index f8650dc..9502b48 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -175,6 +175,24 @@ retry:
        return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+       char *p, *fixed_name;
+
+       fixed_name = kstrdup(name);
+       if (!fixed_name) {
+               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+                               "name \"%s\"\n", name);
+               return name;
+       }
+
+       p = fixed_name;
+       while ((p = strstr(p, "/")))
+               *p++ = '_';
+
+       return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -211,6 +229,9 @@ void proc_device_tree_add_node(struct device_node *np,
                if (duplicate_name(de, p))
                        p = fixup_name(np, de, p);
 
+               if (strstr(p, "/"))
+                       p = unslash_name(p);
+
                ent = __proc_device_tree_add_prop(de, pp, p);
                if (ent == NULL)
                        break;

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -175,6 +175,24 @@ retry:
>         return fixed_name;
>  }
>  
> +static const char *unslash_name(const char *name)
> +{
> +       char *p, *fixed_name;
> +
> +       fixed_name = kstrdup(name);
> +       if (!fixed_name) {
> +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> +                               "name \"%s\"\n", name);
> +               return name;
> +       }
> +
> +       p = fixed_name;
> +       while ((p = strstr(p, "/")))
> +               *p++ = '_';

This is wasteful. :-)
Also, I hope we won't spit message every time allocation fail.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -175,6 +175,24 @@ retry:
>         return fixed_name;
>  }
>  
> +static const char *unslash_name(const char *name)
> +{
> +       char *p, *fixed_name;
> +
> +       fixed_name = kstrdup(name);
> +       if (!fixed_name) {
> +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> +                               "name \"%s\"\n", name);
> +               return name;
> +       }
> +
> +       p = fixed_name;
> +       while ((p = strstr(p, "/")))
> +               *p++ = '_';

This is wasteful. :-)
Also, I hope we won't spit message every time allocation fail.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -175,6 +175,24 @@ retry:
>         return fixed_name;
>  }
>  
> +static const char *unslash_name(const char *name)
> +{
> +       char *p, *fixed_name;
> +
> +       fixed_name = kstrdup(name);
> +       if (!fixed_name) {
> +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> +                               "name \"%s\"\n", name);
> +               return name;
> +       }
> +
> +       p = fixed_name;
> +       while ((p = strstr(p, "/")))
> +               *p++ = '_';

This is wasteful. :-)
Also, I hope we won't spit message every time allocation fail.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Wed, 2010-04-21 at 18:55 +0300, Alexey Dobriyan wrote:
> On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> > On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> > --- a/fs/proc/proc_devtree.c
> > +++ b/fs/proc/proc_devtree.c
> > @@ -175,6 +175,24 @@ retry:
> >         return fixed_name;
> >  }
> >  
> > +static const char *unslash_name(const char *name)
> > +{
> > +       char *p, *fixed_name;
> > +
> > +       fixed_name = kstrdup(name);
> > +       if (!fixed_name) {
> > +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> > +                               "name \"%s\"\n", name);
> > +               return name;
> > +       }
> > +
> > +       p = fixed_name;
> > +       while ((p = strstr(p, "/")))
> > +               *p++ = '_';
> 
> This is wasteful. :-)

Whatever, patches welcome :)

> Also, I hope we won't spit message every time allocation fail.

We do. Your system is mostly hosed anyway, but feel free to rate limit
it or something.

The error handling in there is a bit dubious, if the alloc fails we just
return the old name, which we know is bogus. It should probably return
NULL and the calling code can check - same for fixup_name().

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Wed, 2010-04-21 at 18:55 +0300, Alexey Dobriyan wrote:
> On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> > On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> > --- a/fs/proc/proc_devtree.c
> > +++ b/fs/proc/proc_devtree.c
> > @@ -175,6 +175,24 @@ retry:
> >         return fixed_name;
> >  }
> >  
> > +static const char *unslash_name(const char *name)
> > +{
> > +       char *p, *fixed_name;
> > +
> > +       fixed_name = kstrdup(name);
> > +       if (!fixed_name) {
> > +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> > +                               "name \"%s\"\n", name);
> > +               return name;
> > +       }
> > +
> > +       p = fixed_name;
> > +       while ((p = strstr(p, "/")))
> > +               *p++ = '_';
> 
> This is wasteful. :-)

Whatever, patches welcome :)

> Also, I hope we won't spit message every time allocation fail.

We do. Your system is mostly hosed anyway, but feel free to rate limit
it or something.

The error handling in there is a bit dubious, if the alloc fails we just
return the old name, which we know is bogus. It should probably return
NULL and the calling code can check - same for fixup_name().

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Wed, 2010-04-21 at 18:55 +0300, Alexey Dobriyan wrote:
> On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> > On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> > --- a/fs/proc/proc_devtree.c
> > +++ b/fs/proc/proc_devtree.c
> > @@ -175,6 +175,24 @@ retry:
> >         return fixed_name;
> >  }
> >  
> > +static const char *unslash_name(const char *name)
> > +{
> > +       char *p, *fixed_name;
> > +
> > +       fixed_name = kstrdup(name);
> > +       if (!fixed_name) {
> > +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> > +                               "name \"%s\"\n", name);
> > +               return name;
> > +       }
> > +
> > +       p = fixed_name;
> > +       while ((p = strstr(p, "/")))
> > +               *p++ = '_';
> 
> This is wasteful. :-)

Whatever, patches welcome :)

> Also, I hope we won't spit message every time allocation fail.

We do. Your system is mostly hosed anyway, but feel free to rate limit
it or something.

The error handling in there is a bit dubious, if the alloc fails we just
return the old name, which we know is bogus. It should probably return
NULL and the calling code can check - same for fixup_name().

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Michael Ellerman wrote:
> On Wed, 2010-04-21 at 18:55 +0300, Alexey Dobriyan wrote:
> > On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> > > On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> > > --- a/fs/proc/proc_devtree.c
> > > +++ b/fs/proc/proc_devtree.c
> > > @@ -175,6 +175,24 @@ retry:
> > >         return fixed_name;
> > >  }
> > >  
> > > +static const char *unslash_name(const char *name)
> > > +{
> > > +       char *p, *fixed_name;
> > > +
> > > +       fixed_name = kstrdup(name);
> > > +       if (!fixed_name) {
> > > +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> > > +                               "name \"%s\"\n", name);
> > > +               return name;
> > > +       }
> > > +
> > > +       p = fixed_name;
> > > +       while ((p = strstr(p, "/")))
> > > +               *p++ = '_';
> > 
> > This is wasteful. :-)
> 
> Whatever, patches welcome :)
> 
> > Also, I hope we won't spit message every time allocation fail.
> 
> We do. Your system is mostly hosed anyway, but feel free to rate limit
> it or something.

OK

Is anyone going to post a clean patch for that with a sign-off?

Rafael

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Michael Ellerman wrote:
> On Wed, 2010-04-21 at 18:55 +0300, Alexey Dobriyan wrote:
> > On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> > > On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> > > --- a/fs/proc/proc_devtree.c
> > > +++ b/fs/proc/proc_devtree.c
> > > @@ -175,6 +175,24 @@ retry:
> > >         return fixed_name;
> > >  }
> > >  
> > > +static const char *unslash_name(const char *name)
> > > +{
> > > +       char *p, *fixed_name;
> > > +
> > > +       fixed_name = kstrdup(name);
> > > +       if (!fixed_name) {
> > > +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> > > +                               "name \"%s\"\n", name);
> > > +               return name;
> > > +       }
> > > +
> > > +       p = fixed_name;
> > > +       while ((p = strstr(p, "/")))
> > > +               *p++ = '_';
> > 
> > This is wasteful. :-)
> 
> Whatever, patches welcome :)
> 
> > Also, I hope we won't spit message every time allocation fail.
> 
> We do. Your system is mostly hosed anyway, but feel free to rate limit
> it or something.

OK

Is anyone going to post a clean patch for that with a sign-off?

Rafael

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Michael Ellerman wrote:
> On Wed, 2010-04-21 at 18:55 +0300, Alexey Dobriyan wrote:
> > On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> > > On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> > > --- a/fs/proc/proc_devtree.c
> > > +++ b/fs/proc/proc_devtree.c
> > > @@ -175,6 +175,24 @@ retry:
> > >         return fixed_name;
> > >  }
> > >  
> > > +static const char *unslash_name(const char *name)
> > > +{
> > > +       char *p, *fixed_name;
> > > +
> > > +       fixed_name = kstrdup(name);
> > > +       if (!fixed_name) {
> > > +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> > > +                               "name \"%s\"\n", name);
> > > +               return name;
> > > +       }
> > > +
> > > +       p = fixed_name;
> > > +       while ((p = strstr(p, "/")))
> > > +               *p++ = '_';
> > 
> > This is wasteful. :-)
> 
> Whatever, patches welcome :)
> 
> > Also, I hope we won't spit message every time allocation fail.
> 
> We do. Your system is mostly hosed anyway, but feel free to rate limit
> it or something.

OK

Is anyone going to post a clean patch for that with a sign-off?

Rafael

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -175,6 +175,24 @@ retry:
>         return fixed_name;
>  }
>  
> +static const char *unslash_name(const char *name)
> +{
> +       char *p, *fixed_name;
> +
> +       fixed_name = kstrdup(name);
> +       if (!fixed_name) {
> +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> +                               "name \"%s\"\n", name);
> +               return name;
> +       }
> +
> +       p = fixed_name;
> +       while ((p = strstr(p, "/")))
> +               *p++ = '_';

This is wasteful. :-)
Also, I hope we won't spit message every time allocation fail.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -175,6 +175,24 @@ retry:
>         return fixed_name;
>  }
>  
> +static const char *unslash_name(const char *name)
> +{
> +       char *p, *fixed_name;
> +
> +       fixed_name = kstrdup(name);
> +       if (!fixed_name) {
> +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> +                               "name \"%s\"\n", name);
> +               return name;
> +       }
> +
> +       p = fixed_name;
> +       while ((p = strstr(p, "/")))
> +               *p++ = '_';

This is wasteful. :-)
Also, I hope we won't spit message every time allocation fail.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Tue, Apr 20, 2010 at 10:18:18PM +1000, Michael Ellerman wrote:
> On Mon, 2010-04-19 at 23:45 -0700, Christian Kujau wrote:
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -175,6 +175,24 @@ retry:
>         return fixed_name;
>  }
>  
> +static const char *unslash_name(const char *name)
> +{
> +       char *p, *fixed_name;
> +
> +       fixed_name = kstrdup(name);
> +       if (!fixed_name) {
> +               printk(KERN_ERR "device-tree: Out of memory trying to unslash "
> +                               "name \"%s\"\n", name);
> +               return name;
> +       }
> +
> +       p = fixed_name;
> +       while ((p = strstr(p, "/")))
> +               *p++ = '_';

This is wasteful. :-)
Also, I hope we won't spit message every time allocation fail.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Tue, 20 Apr 2010 at 22:18, Michael Ellerman wrote:
> Try this 100% unbuilt, 100% untested patch.

I added GFP_KERNEL to kstrdup to make the compile error go away:

fs/proc/proc_devtree.c: In function ‘unslash_name’:
fs/proc/proc_devtree.c:183: error: too few arguments to function ‘kstrdup’
make[2]: *** [fs/proc/proc_devtree.o] Error 1
make[1]: *** [fs/proc] Error 2
make: *** [fs] Error 2

And now 2.6.34-rc5 compiles and boots without the warning. Thanks! 
New dmesg and /proc/device-tree on:

  http://nerdbynature.de/bits/2.6.34-rc1/xlate_proc_name/

Alexey mentioned that this is "wasteful" - does it make the kernel slower? 
I have not done any performance tests, but I'd rather stick with the 
warning than make this Powerbook G4 any more slower :-\


Thanks again,
Christian.

diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index ce94801..019581d 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -176,6 +176,24 @@ retry:
 	return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+	char *p, *fixed_name;
+
+	fixed_name = kstrdup(name, GFP_KERNEL);
+	if (!fixed_name) {
+		printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+				"name \"%s\"\n", name);
+	return name;
+	}
+
+	p = fixed_name;
+	while ((p = strstr(p, "/")))
+		*p++ = '_';
+
+	return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -212,6 +230,9 @@ void proc_device_tree_add_node(struct device_node *np,
 		if (duplicate_name(de, p))
 			p = fixup_name(np, de, p);
 
+		if (strstr(p, "/"))
+			p = unslash_name(p);
+
 		ent = __proc_device_tree_add_prop(de, pp, p);
 		if (ent == NULL)
 			break;
-- 
BOFH excuse #369:

Virus transmitted from computer to sysadmins.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Tue, 20 Apr 2010 at 22:18, Michael Ellerman wrote:
> Try this 100% unbuilt, 100% untested patch.

I added GFP_KERNEL to kstrdup to make the compile error go away:

fs/proc/proc_devtree.c: In function ‘unslash_name’:
fs/proc/proc_devtree.c:183: error: too few arguments to function ‘kstrdup’
make[2]: *** [fs/proc/proc_devtree.o] Error 1
make[1]: *** [fs/proc] Error 2
make: *** [fs] Error 2

And now 2.6.34-rc5 compiles and boots without the warning. Thanks! 
New dmesg and /proc/device-tree on:

  http://nerdbynature.de/bits/2.6.34-rc1/xlate_proc_name/

Alexey mentioned that this is "wasteful" - does it make the kernel slower? 
I have not done any performance tests, but I'd rather stick with the 
warning than make this Powerbook G4 any more slower :-\


Thanks again,
Christian.

diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index ce94801..019581d 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -176,6 +176,24 @@ retry:
 	return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+	char *p, *fixed_name;
+
+	fixed_name = kstrdup(name, GFP_KERNEL);
+	if (!fixed_name) {
+		printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+				"name \"%s\"\n", name);
+	return name;
+	}
+
+	p = fixed_name;
+	while ((p = strstr(p, "/")))
+		*p++ = '_';
+
+	return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -212,6 +230,9 @@ void proc_device_tree_add_node(struct device_node *np,
 		if (duplicate_name(de, p))
 			p = fixup_name(np, de, p);
 
+		if (strstr(p, "/"))
+			p = unslash_name(p);
+
 		ent = __proc_device_tree_add_prop(de, pp, p);
 		if (ent == NULL)
 			break;
-- 
BOFH excuse #369:

Virus transmitted from computer to sysadmins.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Tue, 20 Apr 2010 at 22:18, Michael Ellerman wrote:
> Try this 100% unbuilt, 100% untested patch.

I added GFP_KERNEL to kstrdup to make the compile error go away:

fs/proc/proc_devtree.c: In function =E2=80=98unslash_name=E2=80=99:
fs/proc/proc_devtree.c:183: error: too few arguments to function =E2=80=98k=
strdup=E2=80=99
make[2]: *** [fs/proc/proc_devtree.o] Error 1
make[1]: *** [fs/proc] Error 2
make: *** [fs] Error 2

And now 2.6.34-rc5 compiles and boots without the warning. Thanks!=20
New dmesg and /proc/device-tree on:

  http://nerdbynature.de/bits/2.6.34-rc1/xlate_proc_name/

Alexey mentioned that this is "wasteful" - does it make the kernel slower?=
=20
I have not done any performance tests, but I'd rather stick with the=20
warning than make this Powerbook G4 any more slower :-\


Thanks again,
Christian.

diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index ce94801..019581d 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -176,6 +176,24 @@ retry:
 =09return fixed_name;
 }
=20
+static const char *unslash_name(const char *name)
+{
+=09char *p, *fixed_name;
+
+=09fixed_name =3D kstrdup(name, GFP_KERNEL);
+=09if (!fixed_name) {
+=09=09printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+=09=09=09=09"name \"%s\"\n", name);
+=09return name;
+=09}
+
+=09p =3D fixed_name;
+=09while ((p =3D strstr(p, "/")))
+=09=09*p++ =3D '_';
+
+=09return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -212,6 +230,9 @@ void proc_device_tree_add_node(struct device_node *np,
 =09=09if (duplicate_name(de, p))
 =09=09=09p =3D fixup_name(np, de, p);
=20
+=09=09if (strstr(p, "/"))
+=09=09=09p =3D unslash_name(p);
+
 =09=09ent =3D __proc_device_tree_add_prop(de, pp, p);
 =09=09if (ent =3D=3D NULL)
 =09=09=09break;
--=20
BOFH excuse #369:

Virus transmitted from computer to sysadmins.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Andreas Schwab]

Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org> writes:

> +	while ((p = strstr(p, "/")))

You want to use strchr.

Andreas.

-- 
Andreas Schwab, schwab-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Andreas Schwab]

Christian Kujau <lists@nerdbynature.de> writes:

> +	while ((p = strstr(p, "/")))

You want to use strchr.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Andreas Schwab]

Christian Kujau <lists@nerdbynature.de> writes:

> +	while ((p = strstr(p, "/")))

You want to use strchr.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Tue, 2010-04-20 at 11:15 -0700, Christian Kujau wrote:
> On Tue, 20 Apr 2010 at 22:18, Michael Ellerman wrote:
> > Try this 100% unbuilt, 100% untested patch.
> 
> I added GFP_KERNEL to kstrdup to make the compile error go away:
> 
> fs/proc/proc_devtree.c: In function ‘unslash_name’:
> fs/proc/proc_devtree.c:183: error: too few arguments to function ‘kstrdup’
> make[2]: *** [fs/proc/proc_devtree.o] Error 1
> make[1]: *** [fs/proc] Error 2
> make: *** [fs] Error 2

Yeah oops, told you I hadn't built it.

> And now 2.6.34-rc5 compiles and boots without the warning. Thanks! 
> New dmesg and /proc/device-tree on:
> 
>   http://nerdbynature.de/bits/2.6.34-rc1/xlate_proc_name/

Cool, and we see:

./uni-n@f8000000/i2c@f8001000/i2c-bus@1/fan@5c/pulses_rev

Which is the one that needed fixing.

> Alexey mentioned that this is "wasteful" - does it make the kernel slower? 
> I have not done any performance tests, but I'd rather stick with the 
> warning than make this Powerbook G4 any more slower :-\

Maybe a little. It has to check every string to see if it contains a
"/". But then you save the cost of taking an exeception for the WARN,
which might make up the difference. But it's a one time fixup at boot,
so it's not going to be noticeable.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Tue, 2010-04-20 at 11:15 -0700, Christian Kujau wrote:
> On Tue, 20 Apr 2010 at 22:18, Michael Ellerman wrote:
> > Try this 100% unbuilt, 100% untested patch.
> 
> I added GFP_KERNEL to kstrdup to make the compile error go away:
> 
> fs/proc/proc_devtree.c: In function ‘unslash_name’:
> fs/proc/proc_devtree.c:183: error: too few arguments to function ‘kstrdup’
> make[2]: *** [fs/proc/proc_devtree.o] Error 1
> make[1]: *** [fs/proc] Error 2
> make: *** [fs] Error 2

Yeah oops, told you I hadn't built it.

> And now 2.6.34-rc5 compiles and boots without the warning. Thanks! 
> New dmesg and /proc/device-tree on:
> 
>   http://nerdbynature.de/bits/2.6.34-rc1/xlate_proc_name/

Cool, and we see:

./uni-n@f8000000/i2c@f8001000/i2c-bus@1/fan@5c/pulses_rev

Which is the one that needed fixing.

> Alexey mentioned that this is "wasteful" - does it make the kernel slower? 
> I have not done any performance tests, but I'd rather stick with the 
> warning than make this Powerbook G4 any more slower :-\

Maybe a little. It has to check every string to see if it contains a
"/". But then you save the cost of taking an exeception for the WARN,
which might make up the difference. But it's a one time fixup at boot,
so it's not going to be noticeable.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Tue, 2010-04-20 at 11:15 -0700, Christian Kujau wrote:
> On Tue, 20 Apr 2010 at 22:18, Michael Ellerman wrote:
> > Try this 100% unbuilt, 100% untested patch.
> 
> I added GFP_KERNEL to kstrdup to make the compile error go away:
> 
> fs/proc/proc_devtree.c: In function ‘unslash_name’:
> fs/proc/proc_devtree.c:183: error: too few arguments to function ‘kstrdup’
> make[2]: *** [fs/proc/proc_devtree.o] Error 1
> make[1]: *** [fs/proc] Error 2
> make: *** [fs] Error 2

Yeah oops, told you I hadn't built it.

> And now 2.6.34-rc5 compiles and boots without the warning. Thanks! 
> New dmesg and /proc/device-tree on:
> 
>   http://nerdbynature.de/bits/2.6.34-rc1/xlate_proc_name/

Cool, and we see:

./uni-n@f8000000/i2c@f8001000/i2c-bus@1/fan@5c/pulses_rev

Which is the one that needed fixing.

> Alexey mentioned that this is "wasteful" - does it make the kernel slower? 
> I have not done any performance tests, but I'd rather stick with the 
> warning than make this Powerbook G4 any more slower :-\

Maybe a little. It has to check every string to see if it contains a
"/". But then you save the cost of taking an exeception for the WARN,
which might make up the difference. But it's a one time fixup at boot,
so it's not going to be noticeable.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Stefan Lippers-Hollmann]

Hi

On Friday 30 April 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (38 days old)
> Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

This also continues to be a problem with b2c2-flexcop and 2.6.34-rc5-git10:

[   10.119807] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
[   10.129183] flexcop-pci: will use the HW PID filter.
[   10.129187] flexcop-pci: card revision 2
[   10.129195] b2c2_flexcop_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[   10.129239] ------------[ cut here ]------------
[   10.129244] WARNING: at /tmp/buildd/linux-sidux-2.6-2.6.34~rc5/debian/build/source_amd64_none/fs/proc/generic.c:317 __xlate_proc_name+0xb5/0xd0()
[   10.129246] Hardware name: EP45-DS3
[   10.129247] name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
[   10.129248] Modules linked in: b2c2_flexcop_pci(+) ath9k_common b2c2_flexcop v4l1_compat snd_timer radeon(+) dvb_core ar9170usb(+) ath9k_hw snd_seq_device ir_common tveeprom ttm v4l2_compat_ioctl32 snd drm_kms_helper ir_core ath mac80211 soundcore videobuf_dma_sg cx24123 drm i2c_i801 i2c_algo_bit snd_page_alloc videobuf_core cx24113 s5h1420 cfg80211 rfkill evdev i2c_core tpm_tis btcx_risc tpm led_class pcspkr tpm_bios rtc_cmos button rtc_core intel_agp rtc_lib processor ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom sd_mod usbhid hid uhci_hcd firewire_ohci firewire_core ahci r8169 ehci_hcd mii libata crc_itu_t scsi_mod thermal usbcore nls_base [last unloaded: scsi_wait_scan]
[   10.129279] Pid: 1124, comm: modprobe Not tainted 2.6.34-rc5-sidux-amd64 #1
[   10.129281] Call Trace:
[   10.129285]  [<ffffffff8104ba83>] ? warn_slowpath_common+0x73/0xb0
[   10.129287]  [<ffffffff8104bb20>] ? warn_slowpath_fmt+0x40/0x50
[   10.129290]  [<ffffffff8114f545>] ? __xlate_proc_name+0xb5/0xd0
[   10.129292]  [<ffffffff8114fb2e>] ? __proc_create+0x7e/0x150
[   10.129294]  [<ffffffff811504e7>] ? proc_mkdir_mode+0x27/0x60
[   10.129297]  [<ffffffff8109fb55>] ? register_handler_proc+0x115/0x130
[   10.129300]  [<ffffffff8109d4c1>] ? __setup_irq+0x1d1/0x330
[   10.129303]  [<ffffffffa011b160>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
[   10.129305]  [<ffffffff8109d735>] ? request_threaded_irq+0x115/0x1b0
[   10.129308]  [<ffffffffa011b495>] ? flexcop_pci_probe+0x1a5/0x330 [b2c2_flexcop_pci]
[   10.129312]  [<ffffffff811ceef2>] ? local_pci_probe+0x12/0x20
[   10.129314]  [<ffffffff811d02ca>] ? pci_device_probe+0x10a/0x130
[   10.129317]  [<ffffffff8125cdda>] ? driver_sysfs_add+0x5a/0x80
[   10.129320]  [<ffffffff8125cf03>] ? driver_probe_device+0x93/0x190
[   10.129322]  [<ffffffff8125d093>] ? __driver_attach+0x93/0xa0
[   10.129324]  [<ffffffff8125d000>] ? __driver_attach+0x0/0xa0
[   10.129326]  [<ffffffff8125c638>] ? bus_for_each_dev+0x58/0x80
[   10.129328]  [<ffffffff8125be70>] ? bus_add_driver+0xb0/0x250
[   10.129330]  [<ffffffff8125d38a>] ? driver_register+0x6a/0x130
[   10.129332]  [<ffffffff811d056c>] ? __pci_register_driver+0x4c/0xc0
[   10.129335]  [<ffffffffa012e000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[   10.129338]  [<ffffffff81002044>] ? do_one_initcall+0x34/0x1a0
[   10.129341]  [<ffffffff8107d15f>] ? sys_init_module+0xdf/0x260
[   10.129344]  [<ffffffff81009f42>] ? system_call_fastpath+0x16/0x1b
[   10.129345] ---[ end trace 370a62256537c67a ]---
[   10.134144] DVB: registering new adapter (FlexCop Digital TV device)
[   10.135610] b2c2-flexcop: MAC address = 00:d0:d7:0c:83:d6

Regards
	Stefan Lippers-Hollmann

[Bug #15553] Screen backlight doesn't come back on after lid was closed (GM45)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15553
Subject		: Screen backlight doesn't come back on after lid was closed (GM45)
Submitter	:  <bugs@kaijauch.de>
Date		: 2010-03-17 14:35 (34 days old)

[Bug #15553] Screen backlight doesn't come back on after lid was closed (GM45)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15553
Subject		: Screen backlight doesn't come back on after lid was closed (GM45)
Submitter	:  <bugs@kaijauch.de>
Date		: 2010-03-17 14:35 (34 days old)

[Bug #15551] WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15551
Subject		: WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()
Submitter	: Alex Zhavnerchik <alex.vizor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-16 22:03 (35 days old)

[Bug #15551] WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15551
Subject		: WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()
Submitter	: Alex Zhavnerchik <alex.vizor@gmail.com>
Date		: 2010-03-16 22:03 (35 days old)

[Bug #15601] [BUG] SLOB breaks Crypto

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org
Date		: 2010-03-15 13:39 (36 days old)
Message-ID	: <4B9E38AF.70309-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2

[Bug #15601] [BUG] SLOB breaks Crypto

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev@fami-braun.de
Date		: 2010-03-15 13:39 (36 days old)
Message-ID	: <4B9E38AF.70309@fami-braun.de>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2

Re: [Bug #15601] [BUG] SLOB breaks Crypto

[Pekka Enberg]

On Tue, Apr 20, 2010 at 6:19 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15601
> Subject         : [BUG] SLOB breaks Crypto
> Submitter       : michael-dev-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org
> Date            : 2010-03-15 13:39 (36 days old)
> Message-ID      : <4B9E38AF.70309-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org>
> References      : http://marc.info/?l=linux-kernel&m=126866044724539&w=2

Ping?

Re: [Bug #15601] [BUG] SLOB breaks Crypto

[Pekka Enberg]

On Tue, Apr 20, 2010 at 6:19 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15601
> Subject         : [BUG] SLOB breaks Crypto
> Submitter       : michael-dev@fami-braun.de
> Date            : 2010-03-15 13:39 (36 days old)
> Message-ID      : <4B9E38AF.70309@fami-braun.de>
> References      : http://marc.info/?l=linux-kernel&m=126866044724539&w=2

Ping?

Re: [Bug #15601] [BUG] SLOB breaks Crypto

[Matt Mackall]

On Tue, 2010-04-20 at 09:40 +0300, Pekka Enberg wrote:
> On Tue, Apr 20, 2010 at 6:19 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15601
> > Subject         : [BUG] SLOB breaks Crypto
> > Submitter       : michael-dev-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org
> > Date            : 2010-03-15 13:39 (36 days old)
> > Message-ID      : <4B9E38AF.70309-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org>
> > References      : http://marc.info/?l=linux-kernel&m=126866044724539&w=2
> 
> Ping?

This was last in a need-more-info state, if I recall correctly. I
haven't reproduced it.

-- 
http://selenic.com : development and support for Mercurial and Linux

Re: [Bug #15601] [BUG] SLOB breaks Crypto

[Matt Mackall]

On Tue, 2010-04-20 at 09:40 +0300, Pekka Enberg wrote:
> On Tue, Apr 20, 2010 at 6:19 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15601
> > Subject         : [BUG] SLOB breaks Crypto
> > Submitter       : michael-dev@fami-braun.de
> > Date            : 2010-03-15 13:39 (36 days old)
> > Message-ID      : <4B9E38AF.70309@fami-braun.de>
> > References      : http://marc.info/?l=linux-kernel&m=126866044724539&w=2
> 
> Ping?

This was last in a need-more-info state, if I recall correctly. I
haven't reproduced it.

-- 
http://selenic.com : development and support for Mercurial and Linux

[Bug #15661] PROBLEM: crash on halt with 2.6.34-0.16.rc2.git0.fc14.x86_64

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15661
Subject		: PROBLEM: crash on halt with 2.6.34-0.16.rc2.git0.fc14.x86_64
Submitter	: Jon Masters <jonathan@jonmasters.org>
Date		: 2010-03-26 15:29 (25 days old)
Message-ID	: <<1269617372.3779.234.camel@localhost>>
References	: http://marc.info/?l=linux-kernel&m=126961739803949&w=2

[Bug #15590] 2.6.34-rc1: regression: ^Z no longer stops sound

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 7:58 (37 days old)
Message-ID	: <20100314075831.GA13457@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2

[Bug #15664] Graphics hang and kernel backtrace when starting Azureus with Compiz enabled

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci-x0m+Mc+nT7uljOmnV8AmnkElSqmLX1BE@public.gmane.org>
Date		: 2010-04-01 01:09 (19 days old)

[Bug #15664] Graphics hang and kernel backtrace when starting Azureus with Compiz enabled

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date		: 2010-04-01 01:09 (19 days old)

[Bug #15611] Failure with the 2.6.34-rc1 kernel

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15611
Subject		: Failure with the 2.6.34-rc1 kernel
Submitter	: Rupjyoti Sarmah <rsarmah@amcc.com>
Date		: 2010-03-16 15:45 (35 days old)
Message-ID	: <AC311A8E81420D4EBC1F26E6479848FE065B7D3D@SDCEXCHANGE01.ad.amcc.com>
References	: http://marc.info/?l=linux-kernel&m=126875435718396&w=2

[Bug #15659] [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2010-03-25 20:04 (26 days old)
Message-ID	: <201003252104.24965.maciej.rutecki@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2

Re: [Bug #15659] [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Maciej Rutecki]

On wtorek, 20 kwietnia 2010 o 05:19:20 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15659
> Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR*
>  Hangcheck timer elapsed... GPU hung Submitter	: Maciej Rutecki
>  <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-03-25 20:04 (26 days old)
> Message-ID	: <201003252104.24965.maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2
> 

Bug still exists in 2.6.34-rc4
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: [Bug #15659] [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Maciej Rutecki]

On wtorek, 20 kwietnia 2010 o 05:19:20 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15659
> Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR*
>  Hangcheck timer elapsed... GPU hung Submitter	: Maciej Rutecki
>  <maciej.rutecki@gmail.com>
> Date		: 2010-03-25 20:04 (26 days old)
> Message-ID	: <201003252104.24965.maciej.rutecki@gmail.com>
> References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2
> 

Bug still exists in 2.6.34-rc4
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: [Bug #15659] [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Maciej Rutecki wrote:
> On wtorek, 20 kwietnia 2010 o 05:19:20 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15659
> > Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR*
> >  Hangcheck timer elapsed... GPU hung Submitter	: Maciej Rutecki
> >  <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2010-03-25 20:04 (26 days old)
> > Message-ID	: <201003252104.24965.maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2
> > 
> 
> Bug still exists in 2.6.34-rc4

Thanks for the update.

Rafael

Re: [Bug #15659] [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Maciej Rutecki wrote:
> On wtorek, 20 kwietnia 2010 o 05:19:20 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15659
> > Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR*
> >  Hangcheck timer elapsed... GPU hung Submitter	: Maciej Rutecki
> >  <maciej.rutecki@gmail.com>
> > Date		: 2010-03-25 20:04 (26 days old)
> > Message-ID	: <201003252104.24965.maciej.rutecki@gmail.com>
> > References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2
> > 
> 
> Bug still exists in 2.6.34-rc4

Thanks for the update.

Rafael

[Bug #15625] BUG: 2.6.34-rc1, RIP is (null)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15625
Subject		: BUG: 2.6.34-rc1, RIP is (null)
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-03-18 22:22 (33 days old)
Message-ID	: <4BA2A7A9.4080503@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=126895098217351&w=2

[Bug #15610] fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-03-22 15:59 (29 days old)

[Bug #15610] fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel@oracle.com>
Date		: 2010-03-22 15:59 (29 days old)

[Bug #15672] KVM bug, git bisected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15672
Subject		: KVM bug, git bisected
Submitter	: Kent Overstreet <kent.overstreet@gmail.com>
Date		: 2010-03-27 12:43 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
Message-ID	: <4BADFD74.8060904@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126969385121711&w=2

Re: [Bug #15672] KVM bug, git bisected

[Rik van Riel]

On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15672
> Subject		: KVM bug, git bisected
> Submitter	: Kent Overstreet<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-03-27 12:43 (24 days old)
> First-Bad-Commit: http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> Message-ID	:<4BADFD74.8060904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=126969385121711&w=2

Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6

Re: [Bug #15672] KVM bug, git bisected

[Rik van Riel]

On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15672
> Subject		: KVM bug, git bisected
> Submitter	: Kent Overstreet<kent.overstreet@gmail.com>
> Date		: 2010-03-27 12:43 (24 days old)
> First-Bad-Commit: http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> Message-ID	:<4BADFD74.8060904@gmail.com>
> References	: http://marc.info/?l=linux-kernel&m=126969385121711&w=2

Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6

Re: [Bug #15672] KVM bug, git bisected

[Rik van Riel]

On 04/20/2010 05:11 PM, Rik van Riel wrote:
> On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
>> This message has been generated automatically as a part of a summary
>> report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.33. 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=15672
>> Subject : KVM bug, git bisected
>> Submitter : Kent Overstreet<kent.overstreet@gmail.com>
>> Date : 2010-03-27 12:43 (24 days old)
>> First-Bad-Commit:
>> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
>> Message-ID :<4BADFD74.8060904@gmail.com>
>> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
>
> Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6

Never mind me - this is a harmless (but loud) overflow
of PREEMPT_BITS in the preempt count.

Re: [Bug #15672] KVM bug, git bisected

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Rik van Riel wrote:
> On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> >> This message has been generated automatically as a part of a summary
> >> report
> >> of recent regressions.
> >>
> >> The following bug entry is on the current list of known regressions
> >> from 2.6.33. 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=15672
> >> Subject : KVM bug, git bisected
> >> Submitter : Kent Overstreet<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> Date : 2010-03-27 12:43 (24 days old)
> >> First-Bad-Commit:
> >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> >> Message-ID :<4BADFD74.8060904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> >
> > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> 
> Never mind me - this is a harmless (but loud) overflow
> of PREEMPT_BITS in the preempt count.

OK, what am I supposed to do with this entry, then?  Close?

Rafael

Re: [Bug #15672] KVM bug, git bisected

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Rik van Riel wrote:
> On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> >> This message has been generated automatically as a part of a summary
> >> report
> >> of recent regressions.
> >>
> >> The following bug entry is on the current list of known regressions
> >> from 2.6.33. 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=15672
> >> Subject : KVM bug, git bisected
> >> Submitter : Kent Overstreet<kent.overstreet@gmail.com>
> >> Date : 2010-03-27 12:43 (24 days old)
> >> First-Bad-Commit:
> >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> >> Message-ID :<4BADFD74.8060904@gmail.com>
> >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> >
> > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> 
> Never mind me - this is a harmless (but loud) overflow
> of PREEMPT_BITS in the preempt count.

OK, what am I supposed to do with this entry, then?  Close?

Rafael

Re: [Bug #15672] KVM bug, git bisected

[Borislav Petkov]

From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Date: Wed, Apr 21, 2010 at 07:02:02AM +0200

> On Wednesday 21 April 2010, Rik van Riel wrote:
> > On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> > >> This message has been generated automatically as a part of a summary
> > >> report
> > >> of recent regressions.
> > >>
> > >> The following bug entry is on the current list of known regressions
> > >> from 2.6.33. 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=15672
> > >> Subject : KVM bug, git bisected
> > >> Submitter : Kent Overstreet<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > >> Date : 2010-03-27 12:43 (24 days old)
> > >> First-Bad-Commit:
> > >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> > >> Message-ID :<4BADFD74.8060904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> > >
> > > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> > 
> > Never mind me - this is a harmless (but loud) overflow
> > of PREEMPT_BITS in the preempt count.
> 
> OK, what am I supposed to do with this entry, then?  Close?

FWIW, I hit that warning too when chasing the anon_vma regression. It
seems on certain workloads (for me it was several kvm guests) we're
close to max preemption depth.

Anyway, adding some more people to Cc.

-- 
Regards/Gruss,
    Boris.

Re: [Bug #15672] KVM bug, git bisected

[Borislav Petkov]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Wed, Apr 21, 2010 at 07:02:02AM +0200

> On Wednesday 21 April 2010, Rik van Riel wrote:
> > On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> > >> This message has been generated automatically as a part of a summary
> > >> report
> > >> of recent regressions.
> > >>
> > >> The following bug entry is on the current list of known regressions
> > >> from 2.6.33. 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=15672
> > >> Subject : KVM bug, git bisected
> > >> Submitter : Kent Overstreet<kent.overstreet@gmail.com>
> > >> Date : 2010-03-27 12:43 (24 days old)
> > >> First-Bad-Commit:
> > >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> > >> Message-ID :<4BADFD74.8060904@gmail.com>
> > >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> > >
> > > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> > 
> > Never mind me - this is a harmless (but loud) overflow
> > of PREEMPT_BITS in the preempt count.
> 
> OK, what am I supposed to do with this entry, then?  Close?

FWIW, I hit that warning too when chasing the anon_vma regression. It
seems on certain workloads (for me it was several kvm guests) we're
close to max preemption depth.

Anyway, adding some more people to Cc.

-- 
Regards/Gruss,
    Boris.

Re: [Bug #15672] KVM bug, git bisected

[Peter Zijlstra]

On Wed, 2010-04-21 at 08:20 +0200, Borislav Petkov wrote:
> From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
> Date: Wed, Apr 21, 2010 at 07:02:02AM +0200
> 
> > On Wednesday 21 April 2010, Rik van Riel wrote:
> > > On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > > > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> > > >> This message has been generated automatically as a part of a summary
> > > >> report
> > > >> of recent regressions.
> > > >>
> > > >> The following bug entry is on the current list of known regressions
> > > >> from 2.6.33. 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=15672
> > > >> Subject : KVM bug, git bisected
> > > >> Submitter : Kent Overstreet<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > > >> Date : 2010-03-27 12:43 (24 days old)
> > > >> First-Bad-Commit:
> > > >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> > > >> Message-ID :<4BADFD74.8060904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > > >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> > > >
> > > > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> > > 
> > > Never mind me - this is a harmless (but loud) overflow
> > > of PREEMPT_BITS in the preempt count.
> > 
> > OK, what am I supposed to do with this entry, then?  Close?
> 
> FWIW, I hit that warning too when chasing the anon_vma regression. It
> seems on certain workloads (for me it was several kvm guests) we're
> close to max preemption depth.
> 
> Anyway, adding some more people to Cc.

Right, so my proposed solution to this is to make those locks
preemptible, but that's a large and unfinished patch-set.

As it is, its only a warning, nothing really serious should happen, but
the situation does suck.

Re: [Bug #15672] KVM bug, git bisected

[Peter Zijlstra]

On Wed, 2010-04-21 at 08:20 +0200, Borislav Petkov wrote:
> From: "Rafael J. Wysocki" <rjw@sisk.pl>
> Date: Wed, Apr 21, 2010 at 07:02:02AM +0200
> 
> > On Wednesday 21 April 2010, Rik van Riel wrote:
> > > On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > > > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> > > >> This message has been generated automatically as a part of a summary
> > > >> report
> > > >> of recent regressions.
> > > >>
> > > >> The following bug entry is on the current list of known regressions
> > > >> from 2.6.33. 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=15672
> > > >> Subject : KVM bug, git bisected
> > > >> Submitter : Kent Overstreet<kent.overstreet@gmail.com>
> > > >> Date : 2010-03-27 12:43 (24 days old)
> > > >> First-Bad-Commit:
> > > >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> > > >> Message-ID :<4BADFD74.8060904@gmail.com>
> > > >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> > > >
> > > > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> > > 
> > > Never mind me - this is a harmless (but loud) overflow
> > > of PREEMPT_BITS in the preempt count.
> > 
> > OK, what am I supposed to do with this entry, then?  Close?
> 
> FWIW, I hit that warning too when chasing the anon_vma regression. It
> seems on certain workloads (for me it was several kvm guests) we're
> close to max preemption depth.
> 
> Anyway, adding some more people to Cc.

Right, so my proposed solution to this is to make those locks
preemptible, but that's a large and unfinished patch-set.

As it is, its only a warning, nothing really serious should happen, but
the situation does suck.

Re: [Bug #15672] KVM bug, git bisected

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Peter Zijlstra wrote:
> On Wed, 2010-04-21 at 08:20 +0200, Borislav Petkov wrote:
> > From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
> > Date: Wed, Apr 21, 2010 at 07:02:02AM +0200
> > 
> > > On Wednesday 21 April 2010, Rik van Riel wrote:
> > > > On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > > > > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> > > > >> This message has been generated automatically as a part of a summary
> > > > >> report
> > > > >> of recent regressions.
> > > > >>
> > > > >> The following bug entry is on the current list of known regressions
> > > > >> from 2.6.33. 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=15672
> > > > >> Subject : KVM bug, git bisected
> > > > >> Submitter : Kent Overstreet<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > > > >> Date : 2010-03-27 12:43 (24 days old)
> > > > >> First-Bad-Commit:
> > > > >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> > > > >> Message-ID :<4BADFD74.8060904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > > > >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> > > > >
> > > > > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> > > > 
> > > > Never mind me - this is a harmless (but loud) overflow
> > > > of PREEMPT_BITS in the preempt count.
> > > 
> > > OK, what am I supposed to do with this entry, then?  Close?
> > 
> > FWIW, I hit that warning too when chasing the anon_vma regression. It
> > seems on certain workloads (for me it was several kvm guests) we're
> > close to max preemption depth.
> > 
> > Anyway, adding some more people to Cc.
> 
> Right, so my proposed solution to this is to make those locks
> preemptible, but that's a large and unfinished patch-set.
> 
> As it is, its only a warning, nothing really serious should happen, but
> the situation does suck.

I'm not sure if it's worth keeping that listed, though, as the problem is known
and won't be solved before .34 final.

OK to close as "will fix later"?

Rafael

Re: [Bug #15672] KVM bug, git bisected

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Peter Zijlstra wrote:
> On Wed, 2010-04-21 at 08:20 +0200, Borislav Petkov wrote:
> > From: "Rafael J. Wysocki" <rjw@sisk.pl>
> > Date: Wed, Apr 21, 2010 at 07:02:02AM +0200
> > 
> > > On Wednesday 21 April 2010, Rik van Riel wrote:
> > > > On 04/20/2010 05:11 PM, Rik van Riel wrote:
> > > > > On 04/19/2010 11:19 PM, Rafael J. Wysocki wrote:
> > > > >> This message has been generated automatically as a part of a summary
> > > > >> report
> > > > >> of recent regressions.
> > > > >>
> > > > >> The following bug entry is on the current list of known regressions
> > > > >> from 2.6.33. 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=15672
> > > > >> Subject : KVM bug, git bisected
> > > > >> Submitter : Kent Overstreet<kent.overstreet@gmail.com>
> > > > >> Date : 2010-03-27 12:43 (24 days old)
> > > > >> First-Bad-Commit:
> > > > >> http://kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
> > > > >> Message-ID :<4BADFD74.8060904@gmail.com>
> > > > >> References : http://marc.info/?l=linux-kernel&m=126969385121711&w=2
> > > > >
> > > > > Should be fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6
> > > > 
> > > > Never mind me - this is a harmless (but loud) overflow
> > > > of PREEMPT_BITS in the preempt count.
> > > 
> > > OK, what am I supposed to do with this entry, then?  Close?
> > 
> > FWIW, I hit that warning too when chasing the anon_vma regression. It
> > seems on certain workloads (for me it was several kvm guests) we're
> > close to max preemption depth.
> > 
> > Anyway, adding some more people to Cc.
> 
> Right, so my proposed solution to this is to make those locks
> preemptible, but that's a large and unfinished patch-set.
> 
> As it is, its only a warning, nothing really serious should happen, but
> the situation does suck.

I'm not sure if it's worth keeping that listed, though, as the problem is known
and won't be solved before .34 final.

OK to close as "will fix later"?

Rafael

Re: [Bug #15672] KVM bug, git bisected

[Peter Zijlstra]

On Wed, 2010-04-21 at 17:57 +0200, Rafael J. Wysocki wrote:
> 
> OK to close as "will fix later"?
> 
Sure

Re: [Bug #15672] KVM bug, git bisected

[Peter Zijlstra]

On Wed, 2010-04-21 at 17:57 +0200, Rafael J. Wysocki wrote:
> 
> OK to close as "will fix later"?
> 
Sure

[Bug #15671] intel graphic card hanging (Hangcheck timer elapsed... GPU hung)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
Date		: 2010-03-27 16:11 (24 days old)
Message-ID	: <20100327161104.GA12043-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2

[Bug #15671] intel graphic card hanging (Hangcheck timer elapsed... GPU hung)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2010-03-27 16:11 (24 days old)
Message-ID	: <20100327161104.GA12043@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2

[Bug #15668] start_kernel(): bug: interrupts were enabled early

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15668
Subject		: start_kernel(): bug: interrupts were enabled early
Submitter	: Rabin Vincent <rabin@rab.in>
Date		: 2010-03-25 19:53 (26 days old)
First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
Message-ID	: <20100325194100.GA2364@debian>
References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2

Re: [Bug #15668] start_kernel(): bug: interrupts were enabled early

[Rabin Vincent]

On Tue, Apr 20, 2010 at 05:19:21AM +0200, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
> Subject		: start_kernel(): bug: interrupts were enabled early
> Submitter	: Rabin Vincent <rabin-66gdRtMMWGc@public.gmane.org>
> Date		: 2010-03-25 19:53 (26 days old)
> First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
> Message-ID	: <20100325194100.GA2364@debian>
> References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2

This was fixed by 3eac4abaa69949af0e2f64e5c55ee8a22bbdd3e7 ("rwsem
generic spinlock: use IRQ save/restore spinlocks").

Rabin

Re: [Bug #15668] start_kernel(): bug: interrupts were enabled early

[Rabin Vincent]

On Tue, Apr 20, 2010 at 05:19:21AM +0200, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
> Subject		: start_kernel(): bug: interrupts were enabled early
> Submitter	: Rabin Vincent <rabin@rab.in>
> Date		: 2010-03-25 19:53 (26 days old)
> First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
> Message-ID	: <20100325194100.GA2364@debian>
> References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2

This was fixed by 3eac4abaa69949af0e2f64e5c55ee8a22bbdd3e7 ("rwsem
generic spinlock: use IRQ save/restore spinlocks").

Rabin

Re: [Bug #15668] start_kernel(): bug: interrupts were enabled early

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Rabin Vincent wrote:
> On Tue, Apr 20, 2010 at 05:19:21AM +0200, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
> > Subject		: start_kernel(): bug: interrupts were enabled early
> > Submitter	: Rabin Vincent <rabin-66gdRtMMWGc@public.gmane.org>
> > Date		: 2010-03-25 19:53 (26 days old)
> > First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
> > Message-ID	: <20100325194100.GA2364@debian>
> > References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2
> 
> This was fixed by 3eac4abaa69949af0e2f64e5c55ee8a22bbdd3e7 ("rwsem
> generic spinlock: use IRQ save/restore spinlocks").

Thanks, closed.

Rafael

Re: [Bug #15668] start_kernel(): bug: interrupts were enabled early

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Rabin Vincent wrote:
> On Tue, Apr 20, 2010 at 05:19:21AM +0200, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
> > Subject		: start_kernel(): bug: interrupts were enabled early
> > Submitter	: Rabin Vincent <rabin@rab.in>
> > Date		: 2010-03-25 19:53 (26 days old)
> > First-Bad-Commit: http://kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
> > Message-ID	: <20100325194100.GA2364@debian>
> > References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2
> 
> This was fixed by 3eac4abaa69949af0e2f64e5c55ee8a22bbdd3e7 ("rwsem
> generic spinlock: use IRQ save/restore spinlocks").

Thanks, closed.

Rafael

[Bug #15669] INFO: suspicious rcu_dereference_check()

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-03-08 1:26 (43 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2

[Bug #15673] 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Date		: 2010-03-28 11:31 (23 days old)
Message-ID	: <1269775909.5301.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2

[Bug #15673] 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-03-28 11:31 (23 days old)
Message-ID	: <1269775909.5301.4.camel@localhost.localdomain>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2

[Bug #15698] Freeze on power-off / suspend to ram

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15698
Subject		: Freeze on power-off / suspend to ram
Submitter	: arond <hector1987@gmail.com>
Date		: 2010-04-05 13:53 (15 days old)

[Bug #15704] [r8169] WARNING: at net/sched/sch_generic.c

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date		: 2010-03-31 10:21 (20 days old)
Message-ID	: <<20100331102142.GA3294@swordfish.minsk.epam.com>>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2

Re: [Bug #15704] [r8169] WARNING: at net/sched/sch_generic.c

[Sergey Senozhatsky]

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

Hello,

On (04/20/10 05:19), Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
>

.34-rc5-git7

kernel: [12887.906682] pktgen 2.72: Packet Generator for packet performance testing.
kernel: [12938.998730] ------------[ cut here ]------------
kernel: [12938.998741] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0xc1/0x129()
kernel: [12938.998745] Hardware name: F3JC                
kernel: [12938.998748] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
kernel: [12938.998751] Modules linked in: pktgen usb_storage ipv6 snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek asus_laptop sparse_keymap sdhci_pci sdhci snd_hda_intel mmc_core led_class psmouse snd_hda_codec snd_pcm snd_timer snd
soundcore snd_page_alloc serio_raw rng_core sg i2c_i801 evdev r8169 mii usbhid hid uhci_hcd ehci_hcd sr_mod cdrom sd_mod usbcore ata_piix
kernel: [12938.998808] Pid: 4617, comm: kpktgend_0 Not tainted 2.6.34-rc5-dbg-r8169-git7 #97
kernel: [12938.998811] Call Trace:
kernel: [12938.998819]  [<c102e1b2>] warn_slowpath_common+0x65/0x7c
kernel: [12938.998824]  [<c1268085>] ? dev_watchdog+0xc1/0x129
kernel: [12938.998829]  [<c102e1fd>] warn_slowpath_fmt+0x24/0x27
kernel: [12938.998834]  [<c1268085>] dev_watchdog+0xc1/0x129
kernel: [12938.998841]  [<c1040039>] ? __kfifo_from_user_generic+0x30/0x5c
kernel: [12938.998848]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
kernel: [12938.998853]  [<c1036b3c>] run_timer_softirq+0x18f/0x203
kernel: [12938.998858]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
kernel: [12938.998864]  [<c1267fc4>] ? dev_watchdog+0x0/0x129
kernel: [12938.998870]  [<c1032a72>] __do_softirq+0x88/0x10c
kernel: [12938.998875]  [<c1032b25>] do_softirq+0x2f/0x47
kernel: [12938.998883]  [<f8095488>] ? pktgen_xmit+0xd3e/0xe0b [pktgen]
kernel: [12938.998888]  [<c1032d08>] _local_bh_enable_ip+0x8b/0xb3
kernel: [12938.998894]  [<c1032d38>] local_bh_enable_ip+0x8/0xa
kernel: [12938.998900]  [<c12c3818>] _raw_spin_unlock_bh+0x2f/0x32
kernel: [12938.998906]  [<f8095488>] pktgen_xmit+0xd3e/0xe0b [pktgen]
kernel: [12938.998913]  [<c104463c>] ? sched_clock_cpu+0x121/0x131
kernel: [12938.998922]  [<fd1cf5e4>] ? rtl8169_start_xmit+0x0/0x2f9 [r8169]
kernel: [12938.998928]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
kernel: [12938.998934]  [<c1044679>] ? cpu_clock+0x2d/0x4e
kernel: [12938.998941]  [<c104d1f7>] ? put_lock_stats+0xd/0x21
kernel: [12938.998946]  [<c104d2c0>] ? lock_release_holdtime+0xb5/0xba
kernel: [12938.998952]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
kernel: [12938.998959]  [<f809582a>] pktgen_thread_worker+0x170/0x5e8 [pktgen]
kernel: [12938.998965]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
kernel: [12938.998971]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
kernel: [12938.998977]  [<f80956ba>] ? pktgen_thread_worker+0x0/0x5e8 [pktgen]
kernel: [12938.998982]  [<c103f76a>] kthread+0x6a/0x6f
kernel: [12938.998988]  [<c103f700>] ? kthread+0x0/0x6f
kernel: [12938.998994]  [<c1002dc2>] kernel_thread_helper+0x6/0x10
kernel: [12938.998998] ---[ end trace 030ae30a64f8cf05 ]---
kernel: [12939.012657] r8169 0000:02:00.0: eth0: link up
kernel: [12951.012273] r8169 0000:02:00.0: eth0: link up
kernel: [12951.475547] pktgen: interface: eth0 is already stopped



 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
> Subject		: [r8169] WARNING: at net/sched/sch_generic.c
> Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-03-31 10:21 (20 days old)
> Message-ID	: <<20100331102142.GA3294-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>
> References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2
> 
> 


	Sergey

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

Re: [Bug #15704] [r8169] WARNING: at net/sched/sch_generic.c

[Sergey Senozhatsky]

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

Hello,

On (04/20/10 05:19), Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
>

.34-rc5-git7

kernel: [12887.906682] pktgen 2.72: Packet Generator for packet performance testing.
kernel: [12938.998730] ------------[ cut here ]------------
kernel: [12938.998741] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0xc1/0x129()
kernel: [12938.998745] Hardware name: F3JC                
kernel: [12938.998748] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
kernel: [12938.998751] Modules linked in: pktgen usb_storage ipv6 snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek asus_laptop sparse_keymap sdhci_pci sdhci snd_hda_intel mmc_core led_class psmouse snd_hda_codec snd_pcm snd_timer snd
soundcore snd_page_alloc serio_raw rng_core sg i2c_i801 evdev r8169 mii usbhid hid uhci_hcd ehci_hcd sr_mod cdrom sd_mod usbcore ata_piix
kernel: [12938.998808] Pid: 4617, comm: kpktgend_0 Not tainted 2.6.34-rc5-dbg-r8169-git7 #97
kernel: [12938.998811] Call Trace:
kernel: [12938.998819]  [<c102e1b2>] warn_slowpath_common+0x65/0x7c
kernel: [12938.998824]  [<c1268085>] ? dev_watchdog+0xc1/0x129
kernel: [12938.998829]  [<c102e1fd>] warn_slowpath_fmt+0x24/0x27
kernel: [12938.998834]  [<c1268085>] dev_watchdog+0xc1/0x129
kernel: [12938.998841]  [<c1040039>] ? __kfifo_from_user_generic+0x30/0x5c
kernel: [12938.998848]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
kernel: [12938.998853]  [<c1036b3c>] run_timer_softirq+0x18f/0x203
kernel: [12938.998858]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
kernel: [12938.998864]  [<c1267fc4>] ? dev_watchdog+0x0/0x129
kernel: [12938.998870]  [<c1032a72>] __do_softirq+0x88/0x10c
kernel: [12938.998875]  [<c1032b25>] do_softirq+0x2f/0x47
kernel: [12938.998883]  [<f8095488>] ? pktgen_xmit+0xd3e/0xe0b [pktgen]
kernel: [12938.998888]  [<c1032d08>] _local_bh_enable_ip+0x8b/0xb3
kernel: [12938.998894]  [<c1032d38>] local_bh_enable_ip+0x8/0xa
kernel: [12938.998900]  [<c12c3818>] _raw_spin_unlock_bh+0x2f/0x32
kernel: [12938.998906]  [<f8095488>] pktgen_xmit+0xd3e/0xe0b [pktgen]
kernel: [12938.998913]  [<c104463c>] ? sched_clock_cpu+0x121/0x131
kernel: [12938.998922]  [<fd1cf5e4>] ? rtl8169_start_xmit+0x0/0x2f9 [r8169]
kernel: [12938.998928]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
kernel: [12938.998934]  [<c1044679>] ? cpu_clock+0x2d/0x4e
kernel: [12938.998941]  [<c104d1f7>] ? put_lock_stats+0xd/0x21
kernel: [12938.998946]  [<c104d2c0>] ? lock_release_holdtime+0xb5/0xba
kernel: [12938.998952]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
kernel: [12938.998959]  [<f809582a>] pktgen_thread_worker+0x170/0x5e8 [pktgen]
kernel: [12938.998965]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
kernel: [12938.998971]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
kernel: [12938.998977]  [<f80956ba>] ? pktgen_thread_worker+0x0/0x5e8 [pktgen]
kernel: [12938.998982]  [<c103f76a>] kthread+0x6a/0x6f
kernel: [12938.998988]  [<c103f700>] ? kthread+0x0/0x6f
kernel: [12938.998994]  [<c1002dc2>] kernel_thread_helper+0x6/0x10
kernel: [12938.998998] ---[ end trace 030ae30a64f8cf05 ]---
kernel: [12939.012657] r8169 0000:02:00.0: eth0: link up
kernel: [12951.012273] r8169 0000:02:00.0: eth0: link up
kernel: [12951.475547] pktgen: interface: eth0 is already stopped



 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
> Subject		: [r8169] WARNING: at net/sched/sch_generic.c
> Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Date		: 2010-03-31 10:21 (20 days old)
> Message-ID	: <<20100331102142.GA3294@swordfish.minsk.epam.com>>
> References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2
> 
> 


	Sergey

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

Re: [Bug #15704] [r8169] WARNING: at net/sched/sch_generic.c

[Rafael J. Wysocki]

On Monday 26 April 2010, Sergey Senozhatsky wrote:
> Hello,
> 
> On (04/20/10 05:19), Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  Please verify if it still should be listed and let the tracking team
> > know (either way).
> > 
> >
> 
> .34-rc5-git7
> 
> kernel: [12887.906682] pktgen 2.72: Packet Generator for packet performance testing.
> kernel: [12938.998730] ------------[ cut here ]------------
> kernel: [12938.998741] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0xc1/0x129()
> kernel: [12938.998745] Hardware name: F3JC                
> kernel: [12938.998748] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> kernel: [12938.998751] Modules linked in: pktgen usb_storage ipv6 snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek asus_laptop sparse_keymap sdhci_pci sdhci snd_hda_intel mmc_core led_class psmouse snd_hda_codec snd_pcm snd_timer snd
> soundcore snd_page_alloc serio_raw rng_core sg i2c_i801 evdev r8169 mii usbhid hid uhci_hcd ehci_hcd sr_mod cdrom sd_mod usbcore ata_piix
> kernel: [12938.998808] Pid: 4617, comm: kpktgend_0 Not tainted 2.6.34-rc5-dbg-r8169-git7 #97
> kernel: [12938.998811] Call Trace:
> kernel: [12938.998819]  [<c102e1b2>] warn_slowpath_common+0x65/0x7c
> kernel: [12938.998824]  [<c1268085>] ? dev_watchdog+0xc1/0x129
> kernel: [12938.998829]  [<c102e1fd>] warn_slowpath_fmt+0x24/0x27
> kernel: [12938.998834]  [<c1268085>] dev_watchdog+0xc1/0x129
> kernel: [12938.998841]  [<c1040039>] ? __kfifo_from_user_generic+0x30/0x5c
> kernel: [12938.998848]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
> kernel: [12938.998853]  [<c1036b3c>] run_timer_softirq+0x18f/0x203
> kernel: [12938.998858]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
> kernel: [12938.998864]  [<c1267fc4>] ? dev_watchdog+0x0/0x129
> kernel: [12938.998870]  [<c1032a72>] __do_softirq+0x88/0x10c
> kernel: [12938.998875]  [<c1032b25>] do_softirq+0x2f/0x47
> kernel: [12938.998883]  [<f8095488>] ? pktgen_xmit+0xd3e/0xe0b [pktgen]
> kernel: [12938.998888]  [<c1032d08>] _local_bh_enable_ip+0x8b/0xb3
> kernel: [12938.998894]  [<c1032d38>] local_bh_enable_ip+0x8/0xa
> kernel: [12938.998900]  [<c12c3818>] _raw_spin_unlock_bh+0x2f/0x32
> kernel: [12938.998906]  [<f8095488>] pktgen_xmit+0xd3e/0xe0b [pktgen]
> kernel: [12938.998913]  [<c104463c>] ? sched_clock_cpu+0x121/0x131
> kernel: [12938.998922]  [<fd1cf5e4>] ? rtl8169_start_xmit+0x0/0x2f9 [r8169]
> kernel: [12938.998928]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
> kernel: [12938.998934]  [<c1044679>] ? cpu_clock+0x2d/0x4e
> kernel: [12938.998941]  [<c104d1f7>] ? put_lock_stats+0xd/0x21
> kernel: [12938.998946]  [<c104d2c0>] ? lock_release_holdtime+0xb5/0xba
> kernel: [12938.998952]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
> kernel: [12938.998959]  [<f809582a>] pktgen_thread_worker+0x170/0x5e8 [pktgen]
> kernel: [12938.998965]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
> kernel: [12938.998971]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
> kernel: [12938.998977]  [<f80956ba>] ? pktgen_thread_worker+0x0/0x5e8 [pktgen]
> kernel: [12938.998982]  [<c103f76a>] kthread+0x6a/0x6f
> kernel: [12938.998988]  [<c103f700>] ? kthread+0x0/0x6f
> kernel: [12938.998994]  [<c1002dc2>] kernel_thread_helper+0x6/0x10
> kernel: [12938.998998] ---[ end trace 030ae30a64f8cf05 ]---
> kernel: [12939.012657] r8169 0000:02:00.0: eth0: link up
> kernel: [12951.012273] r8169 0000:02:00.0: eth0: link up
> kernel: [12951.475547] pktgen: interface: eth0 is already stopped

Thanks for the update.

Rafael

Re: [Bug #15704] [r8169] WARNING: at net/sched/sch_generic.c

[Rafael J. Wysocki]

On Monday 26 April 2010, Sergey Senozhatsky wrote:
> Hello,
> 
> On (04/20/10 05:19), Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  Please verify if it still should be listed and let the tracking team
> > know (either way).
> > 
> >
> 
> .34-rc5-git7
> 
> kernel: [12887.906682] pktgen 2.72: Packet Generator for packet performance testing.
> kernel: [12938.998730] ------------[ cut here ]------------
> kernel: [12938.998741] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0xc1/0x129()
> kernel: [12938.998745] Hardware name: F3JC                
> kernel: [12938.998748] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> kernel: [12938.998751] Modules linked in: pktgen usb_storage ipv6 snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek asus_laptop sparse_keymap sdhci_pci sdhci snd_hda_intel mmc_core led_class psmouse snd_hda_codec snd_pcm snd_timer snd
> soundcore snd_page_alloc serio_raw rng_core sg i2c_i801 evdev r8169 mii usbhid hid uhci_hcd ehci_hcd sr_mod cdrom sd_mod usbcore ata_piix
> kernel: [12938.998808] Pid: 4617, comm: kpktgend_0 Not tainted 2.6.34-rc5-dbg-r8169-git7 #97
> kernel: [12938.998811] Call Trace:
> kernel: [12938.998819]  [<c102e1b2>] warn_slowpath_common+0x65/0x7c
> kernel: [12938.998824]  [<c1268085>] ? dev_watchdog+0xc1/0x129
> kernel: [12938.998829]  [<c102e1fd>] warn_slowpath_fmt+0x24/0x27
> kernel: [12938.998834]  [<c1268085>] dev_watchdog+0xc1/0x129
> kernel: [12938.998841]  [<c1040039>] ? __kfifo_from_user_generic+0x30/0x5c
> kernel: [12938.998848]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
> kernel: [12938.998853]  [<c1036b3c>] run_timer_softirq+0x18f/0x203
> kernel: [12938.998858]  [<c1036ae3>] ? run_timer_softirq+0x136/0x203
> kernel: [12938.998864]  [<c1267fc4>] ? dev_watchdog+0x0/0x129
> kernel: [12938.998870]  [<c1032a72>] __do_softirq+0x88/0x10c
> kernel: [12938.998875]  [<c1032b25>] do_softirq+0x2f/0x47
> kernel: [12938.998883]  [<f8095488>] ? pktgen_xmit+0xd3e/0xe0b [pktgen]
> kernel: [12938.998888]  [<c1032d08>] _local_bh_enable_ip+0x8b/0xb3
> kernel: [12938.998894]  [<c1032d38>] local_bh_enable_ip+0x8/0xa
> kernel: [12938.998900]  [<c12c3818>] _raw_spin_unlock_bh+0x2f/0x32
> kernel: [12938.998906]  [<f8095488>] pktgen_xmit+0xd3e/0xe0b [pktgen]
> kernel: [12938.998913]  [<c104463c>] ? sched_clock_cpu+0x121/0x131
> kernel: [12938.998922]  [<fd1cf5e4>] ? rtl8169_start_xmit+0x0/0x2f9 [r8169]
> kernel: [12938.998928]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
> kernel: [12938.998934]  [<c1044679>] ? cpu_clock+0x2d/0x4e
> kernel: [12938.998941]  [<c104d1f7>] ? put_lock_stats+0xd/0x21
> kernel: [12938.998946]  [<c104d2c0>] ? lock_release_holdtime+0xb5/0xba
> kernel: [12938.998952]  [<f8095793>] ? pktgen_thread_worker+0xd9/0x5e8 [pktgen]
> kernel: [12938.998959]  [<f809582a>] pktgen_thread_worker+0x170/0x5e8 [pktgen]
> kernel: [12938.998965]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
> kernel: [12938.998971]  [<c103fa46>] ? autoremove_wake_function+0x0/0x2f
> kernel: [12938.998977]  [<f80956ba>] ? pktgen_thread_worker+0x0/0x5e8 [pktgen]
> kernel: [12938.998982]  [<c103f76a>] kthread+0x6a/0x6f
> kernel: [12938.998988]  [<c103f700>] ? kthread+0x0/0x6f
> kernel: [12938.998994]  [<c1002dc2>] kernel_thread_helper+0x6/0x10
> kernel: [12938.998998] ---[ end trace 030ae30a64f8cf05 ]---
> kernel: [12939.012657] r8169 0000:02:00.0: eth0: link up
> kernel: [12951.012273] r8169 0000:02:00.0: eth0: link up
> kernel: [12951.475547] pktgen: interface: eth0 is already stopped

Thanks for the update.

Rafael

[Bug #15711] 2.6.34-rc3, BUG at mm/slab.c:2989

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15711
Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
Submitter	: Heinz Diehl <htd-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
Date		: 2010-04-01 17:52 (19 days old)
Message-ID	: <20100401175225.GA6581-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2

[Bug #15711] 2.6.34-rc3, BUG at mm/slab.c:2989

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15711
Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
Submitter	: Heinz Diehl <htd@fancy-poultry.org>
Date		: 2010-04-01 17:52 (19 days old)
Message-ID	: <20100401175225.GA6581@fancy-poultry.org>
References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2

Re: [Bug #15711] 2.6.34-rc3, BUG at mm/slab.c:2989

[Heinz Diehl]

On 20.04.2010, Rafael J. Wysocki wrote: 

> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15711
> Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
> Submitter	: Heinz Diehl <htd-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
> Date		: 2010-04-01 17:52 (19 days old)
> Message-ID	: <20100401175225.GA6581-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2

Don't know if this is still present, after reporting it here on the list,
I've been advised by Chr. Lameter to switch from slab to slub. I did, and
haven't seen this again.

Re: [Bug #15711] 2.6.34-rc3, BUG at mm/slab.c:2989

[Heinz Diehl]

On 20.04.2010, Rafael J. Wysocki wrote: 

> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15711
> Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
> Submitter	: Heinz Diehl <htd@fancy-poultry.org>
> Date		: 2010-04-01 17:52 (19 days old)
> Message-ID	: <20100401175225.GA6581@fancy-poultry.org>
> References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2

Don't know if this is still present, after reporting it here on the list,
I've been advised by Chr. Lameter to switch from slab to slub. I did, and
haven't seen this again.

[Bug #15712] [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-04-01 6:06 (19 days old)
Message-ID	: <20100401060624.GA1329@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2

[Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi@intel.com>
Date		: 2010-03-25 8:40 (26 days old)
First-Bad-Commit: http://kernel.org/git/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel@alexs-hp.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl@linux-foundation.org>
		  Pekka Enberg <penberg@cs.helsinki.fi>

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Christoph Lameter]

On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:

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

I have not been able to reproduce it so far.

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka Enberg]

Christoph Lameter wrote:
> On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:
> 
>> The following bug entry is on the current list of known regressions
>> from 2.6.33.  Please verify if it still should be listed and let the tracking team
>> know (either way).
> 
> I have not been able to reproduce it so far.

So what are our options? We can revert the SLUB conversion patch for now 
but I still can't see what's wrong with it...

			Pekka

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka Enberg]

Christoph Lameter wrote:
> On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:
> 
>> The following bug entry is on the current list of known regressions
>> from 2.6.33.  Please verify if it still should be listed and let the tracking team
>> know (either way).
> 
> I have not been able to reproduce it so far.

So what are our options? We can revert the SLUB conversion patch for now 
but I still can't see what's wrong with it...

			Pekka

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka J Enberg]

On Thu, 22 Apr 2010, Pekka Enberg wrote:
>>> The following bug entry is on the current list of known regressions
>>> from 2.6.33.  Please verify if it still should be listed and let the 
>>> tracking team
>>> know (either way).
>> 
>> I have not been able to reproduce it so far.
>
> So what are our options? We can revert the SLUB conversion patch for now but 
> I still can't see what's wrong with it...

I haven't been able to reproduce this either on my Core 2 machine.

Yanmin, does something like this help on your machines? I'm thinking false 
sharing with some other per-CPU data structure that happens to be put in 
same percpu slot as struct kmem_cache_cpu...

 			Pekka

diff --git a/mm/slub.c b/mm/slub.c
index 7d6c8b1..d8159d6 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -2066,7 +2066,7 @@ init_kmem_cache_node(struct kmem_cache_node *n, struct kmem_cache *s)
  #endif
  }

-static DEFINE_PER_CPU(struct kmem_cache_cpu, kmalloc_percpu[KMALLOC_CACHES]);
+static DEFINE_PER_CPU_ALIGNED(struct kmem_cache_cpu, kmalloc_percpu[KMALLOC_CACHES]);

  static inline int alloc_kmem_cache_cpus(struct kmem_cache *s, gfp_t flags)
  {
@@ -2077,7 +2077,7 @@ static inline int alloc_kmem_cache_cpus(struct kmem_cache *s, gfp_t flags)
  		 */
  		s->cpu_slab = kmalloc_percpu + (s - kmalloc_caches);
  	else
-		s->cpu_slab =  alloc_percpu(struct kmem_cache_cpu);
+		s->cpu_slab = __alloc_percpu(sizeof(struct kmem_cache_cpu), cache_line_size());

  	if (!s->cpu_slab)
  		return 0;

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Zhang, Yanmin]

On Fri, 2010-04-23 at 22:18 +0300, Pekka J Enberg wrote:
> On Thu, 22 Apr 2010, Pekka Enberg wrote:
> >>> The following bug entry is on the current list of known regressions
> >>> from 2.6.33.  Please verify if it still should be listed and let the 
> >>> tracking team
> >>> know (either way).
> >> 
> >> I have not been able to reproduce it so far.
> >
> > So what are our options? We can revert the SLUB conversion patch for now but 
> > I still can't see what's wrong with it...
I also don't know why. The original patch looks good.

> 
> I haven't been able to reproduce this either on my Core 2 machine.
Mostly, the regression exists on Nehalem machines. I suspect it's related to
hyper-threading machine.

> 
> Yanmin, does something like this help on your machines?
A quick testing doesn't show any help.

I did a new testing. After the machine boots, I hot remove 8 hyper-threading cpu
which means last 8 are just cores. The regression between 2.6.33 and 2.6.34-rc becomes
small.

My opinion is we needn't revert the patch, but still keep an eye on it when testing other
new RC kernel releases. One reason is volanoMark and netperf have no such regression.
Is it ok?

Yanmin

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Zhang, Yanmin]

On Fri, 2010-04-23 at 22:18 +0300, Pekka J Enberg wrote:
> On Thu, 22 Apr 2010, Pekka Enberg wrote:
> >>> The following bug entry is on the current list of known regressions
> >>> from 2.6.33.  Please verify if it still should be listed and let the 
> >>> tracking team
> >>> know (either way).
> >> 
> >> I have not been able to reproduce it so far.
> >
> > So what are our options? We can revert the SLUB conversion patch for now but 
> > I still can't see what's wrong with it...
I also don't know why. The original patch looks good.

> 
> I haven't been able to reproduce this either on my Core 2 machine.
Mostly, the regression exists on Nehalem machines. I suspect it's related to
hyper-threading machine.

> 
> Yanmin, does something like this help on your machines?
A quick testing doesn't show any help.

I did a new testing. After the machine boots, I hot remove 8 hyper-threading cpu
which means last 8 are just cores. The regression between 2.6.33 and 2.6.34-rc becomes
small.

My opinion is we needn't revert the patch, but still keep an eye on it when testing other
new RC kernel releases. One reason is volanoMark and netperf have no such regression.
Is it ok?

Yanmin

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka Enberg]

Hi Yanmin,

On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
<yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
>> I haven't been able to reproduce this either on my Core 2 machine.
> Mostly, the regression exists on Nehalem machines. I suspect it's related to
> hyper-threading machine.

OK, so does anyone know why hyper-threading would change things for
the per-CPU allocator?

>> Yanmin, does something like this help on your machines?
> A quick testing doesn't show any help.

So it's unlikely to be false sharing, I suppose.

> I did a new testing. After the machine boots, I hot remove 8 hyper-threading cpu
> which means last 8 are just cores. The regression between 2.6.33 and 2.6.34-rc becomes
> small.
>
> My opinion is we needn't revert the patch, but still keep an eye on it when testing other
> new RC kernel releases. One reason is volanoMark and netperf have no such regression.
> Is it ok?

We need to get this fixed. In my experience, it's pretty common that
slab regressions pop up only in one or few benchmarks. The problem is
likely to pop up in some real-world workload where it's even more
difficult to track down because basic CPU profiles don't pin-point the
problem.

Do we have some Intel CPU expert hanging around here that could
enlighten me of the effects of hyper-threading on CPU caching? I also
wonder why it's showing up with the new per-CPU allocator and not with
the homebrewn one we had in SLUB previously.

                        Pekka

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka Enberg]

Hi Yanmin,

On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
<yanmin_zhang@linux.intel.com> wrote:
>> I haven't been able to reproduce this either on my Core 2 machine.
> Mostly, the regression exists on Nehalem machines. I suspect it's related to
> hyper-threading machine.

OK, so does anyone know why hyper-threading would change things for
the per-CPU allocator?

>> Yanmin, does something like this help on your machines?
> A quick testing doesn't show any help.

So it's unlikely to be false sharing, I suppose.

> I did a new testing. After the machine boots, I hot remove 8 hyper-threading cpu
> which means last 8 are just cores. The regression between 2.6.33 and 2.6.34-rc becomes
> small.
>
> My opinion is we needn't revert the patch, but still keep an eye on it when testing other
> new RC kernel releases. One reason is volanoMark and netperf have no such regression.
> Is it ok?

We need to get this fixed. In my experience, it's pretty common that
slab regressions pop up only in one or few benchmarks. The problem is
likely to pop up in some real-world workload where it's even more
difficult to track down because basic CPU profiles don't pin-point the
problem.

Do we have some Intel CPU expert hanging around here that could
enlighten me of the effects of hyper-threading on CPU caching? I also
wonder why it's showing up with the new per-CPU allocator and not with
the homebrewn one we had in SLUB previously.

                        Pekka

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Tejun Heo]

Hello,

On 04/26/2010 09:22 AM, Pekka Enberg wrote:
> On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
> <yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
>>> I haven't been able to reproduce this either on my Core 2 machine.
>> Mostly, the regression exists on Nehalem machines. I suspect it's related to
>> hyper-threading machine.
> 
> OK, so does anyone know why hyper-threading would change things for
> the per-CPU allocator?

My wild speculation is that previously the cpu_slub structures of two
neighboring threads ended up on the same cacheline by accident thanks
to the back to back allocation.  W/ the percpu allocator, this no
longer would happen as the allocator groups percpu data together
per-cpu.

Thanks.

-- 
tejun

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Tejun Heo]

Hello,

On 04/26/2010 09:22 AM, Pekka Enberg wrote:
> On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
> <yanmin_zhang@linux.intel.com> wrote:
>>> I haven't been able to reproduce this either on my Core 2 machine.
>> Mostly, the regression exists on Nehalem machines. I suspect it's related to
>> hyper-threading machine.
> 
> OK, so does anyone know why hyper-threading would change things for
> the per-CPU allocator?

My wild speculation is that previously the cpu_slub structures of two
neighboring threads ended up on the same cacheline by accident thanks
to the back to back allocation.  W/ the percpu allocator, this no
longer would happen as the allocator groups percpu data together
per-cpu.

Thanks.

-- 
tejun

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka Enberg]

Hi,

On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
<yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
>>>> I haven't been able to reproduce this either on my Core 2 machine.
>>> Mostly, the regression exists on Nehalem machines. I suspect it's related to
>>> hyper-threading machine.

On 04/26/2010 09:22 AM, Pekka Enberg wrote:
>> OK, so does anyone know why hyper-threading would change things for
>> the per-CPU allocator?

On Mon, Apr 26, 2010 at 1:02 PM, Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> My wild speculation is that previously the cpu_slub structures of two
> neighboring threads ended up on the same cacheline by accident thanks
> to the back to back allocation.  W/ the percpu allocator, this no
> longer would happen as the allocator groups percpu data together
> per-cpu.

Yanmin, do we see a lot of remote frees for your hackbench run? IIRC,
it's the "deactivate_remote_frees" stat when CONFIG_SLAB_STATS is
enabled.

                        Pekka

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka Enberg]

Hi,

On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
<yanmin_zhang@linux.intel.com> wrote:
>>>> I haven't been able to reproduce this either on my Core 2 machine.
>>> Mostly, the regression exists on Nehalem machines. I suspect it's related to
>>> hyper-threading machine.

On 04/26/2010 09:22 AM, Pekka Enberg wrote:
>> OK, so does anyone know why hyper-threading would change things for
>> the per-CPU allocator?

On Mon, Apr 26, 2010 at 1:02 PM, Tejun Heo <tj@kernel.org> wrote:
> My wild speculation is that previously the cpu_slub structures of two
> neighboring threads ended up on the same cacheline by accident thanks
> to the back to back allocation.  W/ the percpu allocator, this no
> longer would happen as the allocator groups percpu data together
> per-cpu.

Yanmin, do we see a lot of remote frees for your hackbench run? IIRC,
it's the "deactivate_remote_frees" stat when CONFIG_SLAB_STATS is
enabled.

                        Pekka

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Tejun Heo]

On 04/26/2010 12:09 PM, Pekka Enberg wrote:
>> My wild speculation is that previously the cpu_slub structures of two
>> neighboring threads ended up on the same cacheline by accident thanks
>> to the back to back allocation.  W/ the percpu allocator, this no
>> longer would happen as the allocator groups percpu data together
>> per-cpu.
> 
> Yanmin, do we see a lot of remote frees for your hackbench run? IIRC,
> it's the "deactivate_remote_frees" stat when CONFIG_SLAB_STATS is
> enabled.

I'm not familiar with the details or scales here so please take
whatever I say with a grain of salt.  For hyperthreading configuration
I think operations don't have to be remote to be affected.  If the
data for cpu0 and cpu1 were on the same cache line, and cpu0 and cpu1
are occupying the same physical core thus sharing all the resources it
would benefit from the sharing whether any operation was remote or not
as it saves the physical processor one cache line.

Thanks.

-- 
tejun

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Tejun Heo]

On 04/26/2010 12:09 PM, Pekka Enberg wrote:
>> My wild speculation is that previously the cpu_slub structures of two
>> neighboring threads ended up on the same cacheline by accident thanks
>> to the back to back allocation.  W/ the percpu allocator, this no
>> longer would happen as the allocator groups percpu data together
>> per-cpu.
> 
> Yanmin, do we see a lot of remote frees for your hackbench run? IIRC,
> it's the "deactivate_remote_frees" stat when CONFIG_SLAB_STATS is
> enabled.

I'm not familiar with the details or scales here so please take
whatever I say with a grain of salt.  For hyperthreading configuration
I think operations don't have to be remote to be affected.  If the
data for cpu0 and cpu1 were on the same cache line, and cpu0 and cpu1
are occupying the same physical core thus sharing all the resources it
would benefit from the sharing whether any operation was remote or not
as it saves the physical processor one cache line.

Thanks.

-- 
tejun

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Pekka J Enberg]

On 04/26/2010 12:09 PM, Pekka Enberg wrote:
>>> My wild speculation is that previously the cpu_slub structures of two
>>> neighboring threads ended up on the same cacheline by accident thanks
>>> to the back to back allocation.  W/ the percpu allocator, this no
>>> longer would happen as the allocator groups percpu data together
>>> per-cpu.
>>
>> Yanmin, do we see a lot of remote frees for your hackbench run? IIRC,
>> it's the "deactivate_remote_frees" stat when CONFIG_SLAB_STATS is
>> enabled.

On Mon, 26 Apr 2010, Tejun Heo wrote:
> I'm not familiar with the details or scales here so please take
> whatever I say with a grain of salt.  For hyperthreading configuration
> I think operations don't have to be remote to be affected.  If the
> data for cpu0 and cpu1 were on the same cache line, and cpu0 and cpu1
> are occupying the same physical core thus sharing all the resources it
> would benefit from the sharing whether any operation was remote or not
> as it saves the physical processor one cache line.

Even if the cacheline is dirtied like in the struct kmem_cache_cpu case? 
If that's the case, don't we want the per-CPU allocator to support 
back to back allocation for cores that are in the same package?

Btw, I focused on remote frees initially before I understood what you 
actually meant and scetched the following untested patch to take advantage 
of the fact that struct kmem_cache_cpu doesn't fill a whole cache line. It 
tries amortize remote free costs by "queuing" objects. It would be 
interesting to see if it helps here (or in the other SLUB regressions like 
netperf and the famous Intel one).

 			Pekka

diff --git a/include/linux/slub_def.h b/include/linux/slub_def.h
index 0249d41..b554a67 100644
--- a/include/linux/slub_def.h
+++ b/include/linux/slub_def.h
@@ -34,10 +34,14 @@ enum stat_item {
  	ORDER_FALLBACK,		/* Number of times fallback was necessary */
  	NR_SLUB_STAT_ITEMS };

+#define SLUB_MAX_NR_REMOTES	5
+
  struct kmem_cache_cpu {
  	void **freelist;	/* Pointer to first free per cpu object */
  	struct page *page;	/* The slab from which we are allocating */
  	int node;		/* The node of the page (or -1 for debug) */
+	int nr_remotes;		/* Number of remotely free'd objects */
+	void *remotelist[SLUB_MAX_NR_REMOTES];	/* List of remotely free'd objects */
  #ifdef CONFIG_SLUB_STATS
  	unsigned stat[NR_SLUB_STAT_ITEMS];
  #endif
diff --git a/mm/slub.c b/mm/slub.c
index 7d6c8b1..e8e5523 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -1480,6 +1480,24 @@ static void deactivate_slab(struct kmem_cache *s, struct kmem_cache_cpu *c)
  	unfreeze_slab(s, page, tail);
  }

+static void __slab_free(struct kmem_cache *s, struct page *page, void *x, unsigned long addr);
+
+static void flush_remotelist(struct kmem_cache *s, struct kmem_cache_cpu *c)
+{
+	int i;
+
+	for (i = 0; i < c->nr_remotes; i++) {
+		struct page *page;
+		void *x;
+
+		x = c->remotelist[i];
+		page = virt_to_head_page(x);
+
+		__slab_free(s, page, x, _RET_IP_);
+	}
+	c->nr_remotes = 0;
+}
+
  static inline void flush_slab(struct kmem_cache *s, struct kmem_cache_cpu *c)
  {
  	stat(s, CPUSLAB_FLUSH);
@@ -1496,7 +1514,12 @@ static inline void __flush_cpu_slab(struct kmem_cache *s, int cpu)
  {
  	struct kmem_cache_cpu *c = per_cpu_ptr(s->cpu_slab, cpu);

-	if (likely(c && c->page))
+	if (unlikely(!c))
+		return;
+
+	flush_remotelist(s, c);
+
+	if (likely(c->page))
  		flush_slab(s, c);
  }

@@ -1709,6 +1732,8 @@ static __always_inline void *slab_alloc(struct kmem_cache *s,

  	local_irq_save(flags);
  	c = __this_cpu_ptr(s->cpu_slab);
+	if (unlikely(c->nr_remotes == SLUB_MAX_NR_REMOTES))
+		flush_remotelist(s, c);
  	object = c->freelist;
  	if (unlikely(!object || !node_match(c, node)))

@@ -1865,8 +1890,12 @@ static __always_inline void slab_free(struct kmem_cache *s,
  		set_freepointer(s, object, c->freelist);
  		c->freelist = object;
  		stat(s, FREE_FASTPATH);
-	} else
-		__slab_free(s, page, x, addr);
+	} else {
+		if (unlikely(c->nr_remotes == SLUB_MAX_NR_REMOTES))
+			flush_remotelist(s, c);
+
+		c->remotelist[c->nr_remotes++] = x;
+	}

  	local_irq_restore(flags);
  }

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Tejun Heo]

Hello, Pekka.

On 04/26/2010 04:17 PM, Pekka J Enberg wrote:
> Even if the cacheline is dirtied like in the struct kmem_cache_cpu case?

If my hypothesis is the case, I don't think dirtying or not would
matter.  It's about two cpus sharing a cache line which usually is a
bad idea but in this case happens to be a good idea because the two
cpus sit on the same cache.

> If that's the case, don't we want the per-CPU allocator to support back
> to back allocation for cores that are in the same package?

I think it's probably gonna be an over-engineering effort.  W/ percpu
allocator the rest of the cacheline would likely be occupied by
another percpu item for the cpu, so it's not really wasted.  It's just
used differently.  It would be good if we have a way to better pack
small hot ones (for the same cpu) into the same cachelines but I don't
think it would be wise to interleave stuff from different cpus.  It's
not like there's only single way to save a cacheline after all.

Thanks.

-- 
tejun

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Tejun Heo]

Hello, Pekka.

On 04/26/2010 04:17 PM, Pekka J Enberg wrote:
> Even if the cacheline is dirtied like in the struct kmem_cache_cpu case?

If my hypothesis is the case, I don't think dirtying or not would
matter.  It's about two cpus sharing a cache line which usually is a
bad idea but in this case happens to be a good idea because the two
cpus sit on the same cache.

> If that's the case, don't we want the per-CPU allocator to support back
> to back allocation for cores that are in the same package?

I think it's probably gonna be an over-engineering effort.  W/ percpu
allocator the rest of the cacheline would likely be occupied by
another percpu item for the cpu, so it's not really wasted.  It's just
used differently.  It would be good if we have a way to better pack
small hot ones (for the same cpu) into the same cachelines but I don't
think it would be wise to interleave stuff from different cpus.  It's
not like there's only single way to save a cacheline after all.

Thanks.

-- 
tejun

Re: [Bug #15713] hackbench regression due to commit 9dfc6e68bfe6e

[Zhang, Yanmin]

On Mon, 2010-04-26 at 13:09 +0300, Pekka Enberg wrote:
> Hi,
> 
> On Mon, Apr 26, 2010 at 9:59 AM, Zhang, Yanmin
> <yanmin_zhang@linux.intel.com> wrote:
> >>>> I haven't been able to reproduce this either on my Core 2 machine.
> >>> Mostly, the regression exists on Nehalem machines. I suspect it's related to
> >>> hyper-threading machine.
> 
> On 04/26/2010 09:22 AM, Pekka Enberg wrote:
> >> OK, so does anyone know why hyper-threading would change things for
> >> the per-CPU allocator?
> 
> On Mon, Apr 26, 2010 at 1:02 PM, Tejun Heo <tj@kernel.org> wrote:
> > My wild speculation is that previously the cpu_slub structures of two
> > neighboring threads ended up on the same cacheline by accident thanks
> > to the back to back allocation.  W/ the percpu allocator, this no
> > longer would happen as the allocator groups percpu data together
> > per-cpu.
> 
> Yanmin, do we see a lot of remote frees for your hackbench run? IIRC,
> it's the "deactivate_remote_frees" stat when CONFIG_SLAB_STATS is
> enabled.

After runing the testing with 2.6.34-rc5:

#slabinfo -AD
Name                   Objects      Alloc       Free   %Fast Fallb O
skbuff_head_cache         2518  800011810  800009770  95  19     0 1
kmalloc-512               1101  800009118  800008441  95  19     0 2
anon_vma_chain            2500     195878     194477  98  13     0 0
vm_area_struct            2487     160755     158908  97  20     0 1
anon_vma                  2645      88626      87637  99  12     0 0

[ymzhang@lkp-ne01 ~]$ cat /sys/kernel/slab/skbuff_head_cache/deactivate_remote_frees
1 C13=1
[ymzhang@lkp-ne01 ~]$ cat /sys/kernel/slab/kmalloc-512/deactivate_remote_frees       
3 C8=2 C15=1


After running testing against 2.6.33 kernel:
#slabinfo -AD
Name                   Objects      Alloc       Free   %Fast Fallb O
kmalloc-1024               961  800011628  800011167  93   1     0 3
skbuff_head_cache         2518  800012055  800010015  93   1     0 1
vm_area_struct            2892     162196     159987  97  19     0 1
names_cache                128      47139      47141  99  97     0 3
kmalloc-64                3612      40180      37287  99  89     0 0
Acpi-State                 816      36301      36301  99  98     0 0

I remember with 2.6.34-rc1, the fast alloc/free are close to the one of 2.6.33.

[Bug #15730] Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15730
Subject		: Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)
Submitter	: Borislav Petkov <bp@alien8.de>
Date		: 2010-04-02 17:59 (18 days old)
Message-ID	: <20100402175937.GA19690@liondog.tnic>
References	: http://marc.info/?l=linux-kernel&m=127023173329741&w=2

Re: [Bug #15730] Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)

[Borislav Petkov]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Tue, Apr 20, 2010 at 05:19:23AM +0200

> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15730
> Subject		: Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)
> Submitter	: Borislav Petkov <bp@alien8.de>
> Date		: 2010-04-02 17:59 (18 days old)
> Message-ID	: <20100402175937.GA19690@liondog.tnic>
> References	: http://marc.info/?l=linux-kernel&m=127023173329741&w=2

Fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6.

-- 
Regards/Gruss,
    Boris.

Re: [Bug #15730] Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Borislav Petkov wrote:
> From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
> Date: Tue, Apr 20, 2010 at 05:19:23AM +0200
> 
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15730
> > Subject		: Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)
> > Submitter	: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
> > Date		: 2010-04-02 17:59 (18 days old)
> > Message-ID	: <20100402175937.GA19690-f9CnO7I+Q6zU6FkGJEIX5A@public.gmane.org>
> > References	: http://marc.info/?l=linux-kernel&m=127023173329741&w=2
> 
> Fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6.

Yup, closed.

Rafael

Re: [Bug #15730] Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Borislav Petkov wrote:
> From: "Rafael J. Wysocki" <rjw@sisk.pl>
> Date: Tue, Apr 20, 2010 at 05:19:23AM +0200
> 
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15730
> > Subject		: Ugly rmap NULL ptr deref oopsie on hibernate (was Linux 2.6.34-rc3)
> > Submitter	: Borislav Petkov <bp@alien8.de>
> > Date		: 2010-04-02 17:59 (18 days old)
> > Message-ID	: <20100402175937.GA19690@liondog.tnic>
> > References	: http://marc.info/?l=linux-kernel&m=127023173329741&w=2
> 
> Fixed by commit ea90002b0fa7bdee86ec22eba1d951f30bf043a6.

Yup, closed.

Rafael

[Bug #15719] virtio_net causing kernel BUG when running under VirtualBox

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15719
Subject		: virtio_net causing kernel BUG when running under VirtualBox
Submitter	: Thomas Müller <thomas-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
Date		: 2010-03-27 14:32 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
Message-ID	: <4BAE1707.2050803-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
Handled-By	: Shirley Ma <mashirle-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

[Bug #15719] virtio_net causing kernel BUG when running under VirtualBox

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15719
Subject		: virtio_net causing kernel BUG when running under VirtualBox
Submitter	: Thomas Müller <thomas@mathtm.de>
Date		: 2010-03-27 14:32 (24 days old)
First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
Message-ID	: <4BAE1707.2050803@mathtm.de>
References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
Handled-By	: Shirley Ma <mashirle@us.ibm.com>

Re: [Bug #15719] virtio_net causing kernel BUG when running under VirtualBox

[Thomas Müller]

Fixed by commit 0e413f22e4c1cbfe12907e462a7d739a2e316f2b.

Regards
Thomas

On 20.04.2010 05:19, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15719
> Subject		: virtio_net causing kernel BUG when running under VirtualBox
> Submitter	: Thomas Müller <thomas-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
> Date		: 2010-03-27 14:32 (24 days old)
> First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
> Message-ID	: <4BAE1707.2050803-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
> Handled-By	: Shirley Ma <mashirle-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> 
> 

Re: [Bug #15719] virtio_net causing kernel BUG when running under VirtualBox

[Thomas Müller]

Fixed by commit 0e413f22e4c1cbfe12907e462a7d739a2e316f2b.

Regards
Thomas

On 20.04.2010 05:19, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15719
> Subject		: virtio_net causing kernel BUG when running under VirtualBox
> Submitter	: Thomas Müller <thomas@mathtm.de>
> Date		: 2010-03-27 14:32 (24 days old)
> First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
> Message-ID	: <4BAE1707.2050803@mathtm.de>
> References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
> Handled-By	: Shirley Ma <mashirle@us.ibm.com>
> 
> 

Re: [Bug #15719] virtio_net causing kernel BUG when running under VirtualBox

[Rafael J. Wysocki]

On Friday 23 April 2010, Thomas Müller wrote:
> Fixed by commit 0e413f22e4c1cbfe12907e462a7d739a2e316f2b.

Thanks, closing.

Rafael


> On 20.04.2010 05:19, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15719
> > Subject		: virtio_net causing kernel BUG when running under VirtualBox
> > Submitter	: Thomas Müller <thomas-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
> > Date		: 2010-03-27 14:32 (24 days old)
> > First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
> > Message-ID	: <4BAE1707.2050803-5bHTHlrcoh6zQB+pC5nmwQ@public.gmane.org>
> > References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
> > Handled-By	: Shirley Ma <mashirle-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> > 
> > 
> 
> 
> 

Re: [Bug #15719] virtio_net causing kernel BUG when running under VirtualBox

[Rafael J. Wysocki]

On Friday 23 April 2010, Thomas Müller wrote:
> Fixed by commit 0e413f22e4c1cbfe12907e462a7d739a2e316f2b.

Thanks, closing.

Rafael


> On 20.04.2010 05:19, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15719
> > Subject		: virtio_net causing kernel BUG when running under VirtualBox
> > Submitter	: Thomas Müller <thomas@mathtm.de>
> > Date		: 2010-03-27 14:32 (24 days old)
> > First-Bad-Commit: http://kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
> > Message-ID	: <4BAE1707.2050803@mathtm.de>
> > References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
> > Handled-By	: Shirley Ma <mashirle@us.ibm.com>
> > 
> > 
> 
> 
> 

[Bug #15729] BUG: physmap modprobe & rmmod

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15729
Subject		: BUG: physmap modprobe & rmmod
Submitter	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-04-02 20:40 (18 days old)
Message-ID	: <20100402134058.c4682716.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2

[Bug #15729] BUG: physmap modprobe & rmmod

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15729
Subject		: BUG: physmap modprobe & rmmod
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-04-02 20:40 (18 days old)
Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2

Re: [Bug #15729] BUG: physmap modprobe & rmmod

[Wolfram Sang]

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

On Tue, Apr 20, 2010 at 05:19:23AM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15729
> Subject		: BUG: physmap modprobe & rmmod
> Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
> Date		: 2010-04-02 20:40 (18 days old)
> Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
> References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2

Patch is here:

	https://patchwork.kernel.org/patch/90497/

I'd ack it if I still had the original mail :)

CCing linux-mtd and some more people, so it can get picked up.

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

Re: [Bug #15729] BUG: physmap modprobe & rmmod

[Wolfram Sang]

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

On Tue, Apr 20, 2010 at 05:19:23AM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15729
> Subject		: BUG: physmap modprobe & rmmod
> Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
> Date		: 2010-04-02 20:40 (18 days old)
> Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
> References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2

Patch is here:

	https://patchwork.kernel.org/patch/90497/

I'd ack it if I still had the original mail :)

CCing linux-mtd and some more people, so it can get picked up.

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

Re: [Bug #15729] BUG: physmap modprobe & rmmod

[Randy Dunlap]

On Tue, 20 Apr 2010 06:53:01 +0200 Wolfram Sang wrote:

> On Tue, Apr 20, 2010 at 05:19:23AM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15729
> > Subject		: BUG: physmap modprobe & rmmod
> > Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
> > Date		: 2010-04-02 20:40 (18 days old)
> > Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
> > References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2
> 
> Patch is here:
> 
> 	https://patchwork.kernel.org/patch/90497/

Thanks.

> I'd ack it if I still had the original mail :)

I already replied with
Tested-by: Randy Dunlap <randy.dunlap@oracle.com>

> CCing linux-mtd and some more people, so it can get picked up.


---
~Randy

Re: [Bug #15729] BUG: physmap modprobe & rmmod

[Randy Dunlap]

On Tue, 20 Apr 2010 06:53:01 +0200 Wolfram Sang wrote:

> On Tue, Apr 20, 2010 at 05:19:23AM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15729
> > Subject		: BUG: physmap modprobe & rmmod
> > Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
> > Date		: 2010-04-02 20:40 (18 days old)
> > Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
> > References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2
> 
> Patch is here:
> 
> 	https://patchwork.kernel.org/patch/90497/

Thanks.

> I'd ack it if I still had the original mail :)

I already replied with
Tested-by: Randy Dunlap <randy.dunlap@oracle.com>

> CCing linux-mtd and some more people, so it can get picked up.


---
~Randy

[Bug #15744] [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15744
Subject		: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)
Submitter	: Andy Isaacson <adi@hexapodia.org>
Date		: 2010-04-06 22:54 (14 days old)
Message-ID	: <<4BC51312.6080302@oracle.com></desc>>
References	: http://marc.info/?l=linux-kernel&m=127059449031511&w=2

[Bug #15717] bluetooth oops

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-14 20:14 (37 days old)
Message-ID	: <20100314201434.GE22059-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>

[Bug #15717] bluetooth oops

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 20:14 (37 days old)
Message-ID	: <20100314201434.GE22059@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>

[Bug #15790] Meta-Bug: Regressions

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15790
Subject		: Meta-Bug: Regressions
Submitter	: Florian Mickler <fmickler-Mmb7MZpHnFY@public.gmane.org>
Date		: 2010-04-15 18:21 (5 days old)

[Bug #15790] Meta-Bug: Regressions

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15790
Subject		: Meta-Bug: Regressions
Submitter	: Florian Mickler <fmickler@gmx.de>
Date		: 2010-04-15 18:21 (5 days old)

[Bug #15788] external usb sound card doesn't work after resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15788
Subject		: external usb sound card doesn't work after resume
Submitter	: François Valenduc <francois.valenduc-bmtTS95sd5BUM80lpFwj4w@public.gmane.org>
Date		: 2010-04-15 10:16 (5 days old)

[Bug #15788] external usb sound card doesn't work after resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15788
Subject		: external usb sound card doesn't work after resume
Submitter	: François Valenduc <francois.valenduc@tvcablenet.be>
Date		: 2010-04-15 10:16 (5 days old)

[Bug #15768] Incorrectly calculated free blocks result in ENOSPC from writepage

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15768
Subject		: Incorrectly calculated free blocks result in ENOSPC from writepage
Submitter	: Dmitry Monakhov <dmonakhov@openvz.org>
Date		: 2010-04-12 11:24 (8 days old)

[Bug #15774] 2.6.34-rc3: eth0 (8139too): transmit queue 0 timed out

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15774
Subject		: 2.6.34-rc3: eth0 (8139too): transmit queue 0 timed out
Submitter	: Németh Márton <nm127@freemail.hu>
Date		: 2010-04-10 12:33 (10 days old)
Message-ID	: <4BC07022.6000708@freemail.hu>
References	: http://marc.info/?l=linux-kernel&m=127090287021976&w=2

[Bug #15796] [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15796
Subject		: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0
Submitter	: Éric Piel <Eric.Piel@tremplin-utc.net>
Date		: 2010-04-13 21:54 (7 days old)
First-Bad-Commit: http://kernel.org/git/linus/7b3a177b0d4f92b3431b8dca777313a07533a710
Message-ID	: <4BC4E812.6050602@tremplin-utc.net>
References	: http://marc.info/?l=linux-kernel&m=127119569009790&w=2
Handled-By	: Takashi Iwai <tiwai@suse.de>

[Bug #15796] [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15796
Subject		: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0
Submitter	: Éric Piel <Eric.Piel@tremplin-utc.net>
Date		: 2010-04-13 21:54 (7 days old)
First-Bad-Commit: http://kernel.org/git/linus/7b3a177b0d4f92b3431b8dca777313a07533a710
Message-ID	: <4BC4E812.6050602@tremplin-utc.net>
References	: http://marc.info/?l=linux-kernel&m=127119569009790&w=2
Handled-By	: Takashi Iwai <tiwai@suse.de>

[Bug #15795] 2.6.34-rc4 : OOPS in unmap_vma

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15795
Subject		: 2.6.34-rc4 : OOPS in unmap_vma
Submitter	: Parag Warudkar <parag.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-14 (6 days old)
Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2

[Bug #15795] 2.6.34-rc4 : OOPS in unmap_vma

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15795
Subject		: 2.6.34-rc4 : OOPS in unmap_vma
Submitter	: Parag Warudkar <parag.lkml@gmail.com>
Date		: 2010-04-14 (6 days old)
Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2

Re: [Bug #15795] 2.6.34-rc4 : OOPS in unmap_vma

[Parag Warudkar]

On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15795
> Subject		: 2.6.34-rc4 : OOPS in unmap_vma
> Submitter	: Parag Warudkar <parag.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-04-14 (6 days old)
> Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
> References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2
> 
> 
> 

Hasn't reproduced after many retries and I am not sure it can be called a 
regression, may be it's always been there, just not reproducible easily - 
let's close this, I will reopen if needed.

Thanks,

Parag

Re: [Bug #15795] 2.6.34-rc4 : OOPS in unmap_vma

[Parag Warudkar]

On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15795
> Subject		: 2.6.34-rc4 : OOPS in unmap_vma
> Submitter	: Parag Warudkar <parag.lkml@gmail.com>
> Date		: 2010-04-14 (6 days old)
> Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
> References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2
> 
> 
> 

Hasn't reproduced after many retries and I am not sure it can be called a 
regression, may be it's always been there, just not reproducible easily - 
let's close this, I will reopen if needed.

Thanks,

Parag

Re: [Bug #15795] 2.6.34-rc4 : OOPS in unmap_vma

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Parag Warudkar wrote:
> 
> On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:
> 
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15795
> > Subject		: 2.6.34-rc4 : OOPS in unmap_vma
> > Submitter	: Parag Warudkar <parag.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2010-04-14 (6 days old)
> > Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
> > References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2
> > 
> > 
> > 
> 
> Hasn't reproduced after many retries and I am not sure it can be called a 
> regression, may be it's always been there, just not reproducible easily - 
> let's close this, I will reopen if needed.

Done.

Rafael

Re: [Bug #15795] 2.6.34-rc4 : OOPS in unmap_vma

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Parag Warudkar wrote:
> 
> On Tue, 20 Apr 2010, Rafael J. Wysocki wrote:
> 
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15795
> > Subject		: 2.6.34-rc4 : OOPS in unmap_vma
> > Submitter	: Parag Warudkar <parag.lkml@gmail.com>
> > Date		: 2010-04-14 (6 days old)
> > Message-ID	: <alpine.DEB.2.00.1004132147260.1881@parag-laptop>
> > References	: http://marc.info/?l=linux-kernel&m=127121006625429&w=2
> > 
> > 
> > 
> 
> Hasn't reproduced after many retries and I am not sure it can be called a 
> regression, may be it's always been there, just not reproducible easily - 
> let's close this, I will reopen if needed.

Done.

Rafael

[Bug #15805] reiserfs locking

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-15 21:02 (5 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2

[Bug #15805] reiserfs locking

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2010-04-15 21:02 (5 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2

Re: [Bug #15805] reiserfs locking

[Frederic Weisbecker]

On Tue, Apr 20, 2010 at 05:19:25AM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15805
> Subject		: reiserfs locking
> Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-04-15 21:02 (5 days old)
> Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2


That doesn't look like related to the bkl removal.

In fact what I wonder is how we missed that before.

vfs_readdir() take the directory inode mutex
    |
    ------- copy_to_user() takes the mm->mmap_sem

sys_unmap() takes mm->mmap_sem
    |
    ------- reiserfs_file_release() takes inode mutex


The lock inversion can not happen as sys_getdents() can't be called
after the directory is closed.

I'm not sure what to do. Adding more people in Cc.

Re: [Bug #15805] reiserfs locking

[Frederic Weisbecker]

On Tue, Apr 20, 2010 at 05:19:25AM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15805
> Subject		: reiserfs locking
> Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> Date		: 2010-04-15 21:02 (5 days old)
> Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
> References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2


That doesn't look like related to the bkl removal.

In fact what I wonder is how we missed that before.

vfs_readdir() take the directory inode mutex
    |
    ------- copy_to_user() takes the mm->mmap_sem

sys_unmap() takes mm->mmap_sem
    |
    ------- reiserfs_file_release() takes inode mutex


The lock inversion can not happen as sys_getdents() can't be called
after the directory is closed.

I'm not sure what to do. Adding more people in Cc.

[Bug #15812] utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15812
Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
Submitter	:  <adi-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
Date		: 2010-04-19 21:28 (1 days old)

[Bug #15812] utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15812
Subject		: utsname.domainname not set in x86_32 processes (causing "YPBINDPROC_DOMAIN: domain not bound" errors)
Submitter	:  <adi@hexapodia.org>
Date		: 2010-04-19 21:28 (1 days old)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> If you know of any other unresolved regressions from 2.6.33, 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.

Please list these two similar regressions from 2.6.33 in the r600 DRM:

 * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
           https://bugs.freedesktop.org/show_bug.cgi?id=27571

 * r600 CS checker rejects narrow FBO renderbuffers:
           https://bugs.freedesktop.org/show_bug.cgi?id=27609

Thanks.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Nick Bowler wrote:
> On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> > If you know of any other unresolved regressions from 2.6.33, 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.
> 
> Please list these two similar regressions from 2.6.33 in the r600 DRM:
> 
>  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
>            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> 
>  * r600 CS checker rejects narrow FBO renderbuffers:
>            https://bugs.freedesktop.org/show_bug.cgi?id=27609

Do you want to me to add them as one entry or as two separate bugs?

Rafael

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Nick Bowler wrote:
> On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> > If you know of any other unresolved regressions from 2.6.33, 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.
> 
> Please list these two similar regressions from 2.6.33 in the r600 DRM:
> 
>  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
>            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> 
>  * r600 CS checker rejects narrow FBO renderbuffers:
>            https://bugs.freedesktop.org/show_bug.cgi?id=27609

Do you want to me to add them as one entry or as two separate bugs?

Rafael

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Jerome Glisse]

On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> On Tuesday 20 April 2010, Nick Bowler wrote:
> > On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> > > If you know of any other unresolved regressions from 2.6.33, 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.
> > 
> > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > 
> >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > 
> >  * r600 CS checker rejects narrow FBO renderbuffers:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> 
> Do you want to me to add them as one entry or as two separate bugs?
> 
> Rafael
> 

First one is userspace bug, i need to look into the second one.
ie we were lucky the hw didn't lockup without depth buffer and
depth test enabled.

Cheers,
Jerome

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Jerome Glisse]

On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> On Tuesday 20 April 2010, Nick Bowler wrote:
> > On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> > > If you know of any other unresolved regressions from 2.6.33, 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.
> > 
> > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > 
> >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > 
> >  * r600 CS checker rejects narrow FBO renderbuffers:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> 
> Do you want to me to add them as one entry or as two separate bugs?
> 
> Rafael
> 

First one is userspace bug, i need to look into the second one.
ie we were lucky the hw didn't lockup without depth buffer and
depth test enabled.

Cheers,
Jerome

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> On Tuesday 20 April 2010, Nick Bowler wrote:
> > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > 
> >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > 
> >  * r600 CS checker rejects narrow FBO renderbuffers:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> 
> Do you want to me to add them as one entry or as two separate bugs?

As upstream doesn't consider the first to be a kernel issue, I guess you
should just list the second.

On 10:57 Wed 21 Apr     , Jerome Glisse wrote:
> First one is userspace bug, i need to look into the second one.
> ie we were lucky the hw didn't lockup without depth buffer and
> depth test enabled.

OK, if the failure is due to userspace is doing Very Bad Things(tm),
catching that seems reasonable.

Nevertheless, even if it happened by luck, the result was (ostensibly)
working programs that suddenly break once one "upgrades" to the latest
kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
a less cryptic log message would be appropriate?

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> On Tuesday 20 April 2010, Nick Bowler wrote:
> > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > 
> >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > 
> >  * r600 CS checker rejects narrow FBO renderbuffers:
> >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> 
> Do you want to me to add them as one entry or as two separate bugs?

As upstream doesn't consider the first to be a kernel issue, I guess you
should just list the second.

On 10:57 Wed 21 Apr     , Jerome Glisse wrote:
> First one is userspace bug, i need to look into the second one.
> ie we were lucky the hw didn't lockup without depth buffer and
> depth test enabled.

OK, if the failure is due to userspace is doing Very Bad Things(tm),
catching that seems reasonable.

Nevertheless, even if it happened by luck, the result was (ostensibly)
working programs that suddenly break once one "upgrades" to the latest
kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
a less cryptic log message would be appropriate?

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Jerome Glisse]

On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> > On Tuesday 20 April 2010, Nick Bowler wrote:
> > > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > > 
> > >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > > 
> > >  * r600 CS checker rejects narrow FBO renderbuffers:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> > 
> > Do you want to me to add them as one entry or as two separate bugs?
> 
> As upstream doesn't consider the first to be a kernel issue, I guess you
> should just list the second.
> 
> On 10:57 Wed 21 Apr     , Jerome Glisse wrote:
> > First one is userspace bug, i need to look into the second one.
> > ie we were lucky the hw didn't lockup without depth buffer and
> > depth test enabled.
> 
> OK, if the failure is due to userspace is doing Very Bad Things(tm),
> catching that seems reasonable.
> 
> Nevertheless, even if it happened by luck, the result was (ostensibly)
> working programs that suddenly break once one "upgrades" to the latest
> kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> a less cryptic log message would be appropriate?
> 
> -- 
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

I pushed fix into mesa for the depth issue i will look into the other
one today and likely push kernel fix.

Cheers,
Jerome

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Jerome Glisse]

On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> > On Tuesday 20 April 2010, Nick Bowler wrote:
> > > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > > 
> > >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > > 
> > >  * r600 CS checker rejects narrow FBO renderbuffers:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> > 
> > Do you want to me to add them as one entry or as two separate bugs?
> 
> As upstream doesn't consider the first to be a kernel issue, I guess you
> should just list the second.
> 
> On 10:57 Wed 21 Apr     , Jerome Glisse wrote:
> > First one is userspace bug, i need to look into the second one.
> > ie we were lucky the hw didn't lockup without depth buffer and
> > depth test enabled.
> 
> OK, if the failure is due to userspace is doing Very Bad Things(tm),
> catching that seems reasonable.
> 
> Nevertheless, even if it happened by luck, the result was (ostensibly)
> working programs that suddenly break once one "upgrades" to the latest
> kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> a less cryptic log message would be appropriate?
> 
> -- 
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

I pushed fix into mesa for the depth issue i will look into the other
one today and likely push kernel fix.

Cheers,
Jerome

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On 12:23 Fri 23 Apr     , Jerome Glisse wrote:
> On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> > OK, if the failure is due to userspace is doing Very Bad Things(tm),
> > catching that seems reasonable.
> > 
> > Nevertheless, even if it happened by luck, the result was (ostensibly)
> > working programs that suddenly break once one "upgrades" to the latest
> > kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> > a less cryptic log message would be appropriate?
> 
> I pushed fix into mesa for the depth issue i will look into the other
> one today and likely push kernel fix.

Great, thanks.  I'll try out the depth fix tonight.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On 12:23 Fri 23 Apr     , Jerome Glisse wrote:
> On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> > OK, if the failure is due to userspace is doing Very Bad Things(tm),
> > catching that seems reasonable.
> > 
> > Nevertheless, even if it happened by luck, the result was (ostensibly)
> > working programs that suddenly break once one "upgrades" to the latest
> > kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> > a less cryptic log message would be appropriate?
> 
> I pushed fix into mesa for the depth issue i will look into the other
> one today and likely push kernel fix.

Great, thanks.  I'll try out the depth fix tonight.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On 12:23 Fri 23 Apr     , Jerome Glisse wrote:
> On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> > OK, if the failure is due to userspace is doing Very Bad Things(tm),
> > catching that seems reasonable.
> > 
> > Nevertheless, even if it happened by luck, the result was (ostensibly)
> > working programs that suddenly break once one "upgrades" to the latest
> > kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> > a less cryptic log message would be appropriate?
> 
> I pushed fix into mesa for the depth issue i will look into the other
> one today and likely push kernel fix.

Great, thanks.  I'll try out the depth fix tonight.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Jerome Glisse]

On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> > On Tuesday 20 April 2010, Nick Bowler wrote:
> > > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > > 
> > >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > > 
> > >  * r600 CS checker rejects narrow FBO renderbuffers:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> > 
> > Do you want to me to add them as one entry or as two separate bugs?
> 
> As upstream doesn't consider the first to be a kernel issue, I guess you
> should just list the second.
> 
> On 10:57 Wed 21 Apr     , Jerome Glisse wrote:
> > First one is userspace bug, i need to look into the second one.
> > ie we were lucky the hw didn't lockup without depth buffer and
> > depth test enabled.
> 
> OK, if the failure is due to userspace is doing Very Bad Things(tm),
> catching that seems reasonable.
> 
> Nevertheless, even if it happened by luck, the result was (ostensibly)
> working programs that suddenly break once one "upgrades" to the latest
> kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> a less cryptic log message would be appropriate?
> 
> -- 
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

I pushed fix into mesa for the depth issue i will look into the other
one today and likely push kernel fix.

Cheers,
Jerome

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Jerome Glisse]

On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote:
> On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote:
> > On Tuesday 20 April 2010, Nick Bowler wrote:
> > > Please list these two similar regressions from 2.6.33 in the r600 DRM:
> > > 
> > >  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> > > 
> > >  * r600 CS checker rejects narrow FBO renderbuffers:
> > >            https://bugs.freedesktop.org/show_bug.cgi?id=27609
> > 
> > Do you want to me to add them as one entry or as two separate bugs?
> 
> As upstream doesn't consider the first to be a kernel issue, I guess you
> should just list the second.
> 
> On 10:57 Wed 21 Apr     , Jerome Glisse wrote:
> > First one is userspace bug, i need to look into the second one.
> > ie we were lucky the hw didn't lockup without depth buffer and
> > depth test enabled.
> 
> OK, if the failure is due to userspace is doing Very Bad Things(tm),
> catching that seems reasonable.
> 
> Nevertheless, even if it happened by luck, the result was (ostensibly)
> working programs that suddenly break once one "upgrades" to the latest
> kernel.  If userspace can't be fixed before 2.6.34 is released, perhaps
> a less cryptic log message would be appropriate?
> 
> -- 
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

I pushed fix into mesa for the depth issue i will look into the other
one today and likely push kernel fix.

Cheers,
Jerome

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Tuesday 20 April 2010, Nick Bowler wrote:
> On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> > If you know of any other unresolved regressions from 2.6.33, 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.
> 
> Please list these two similar regressions from 2.6.33 in the r600 DRM:
> 
>  * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
>            https://bugs.freedesktop.org/show_bug.cgi?id=27571
> 
>  * r600 CS checker rejects narrow FBO renderbuffers:
>            https://bugs.freedesktop.org/show_bug.cgi?id=27609

Do you want to me to add them as one entry or as two separate bugs?

Rafael

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Nick Bowler]

On 05:15 Tue 20 Apr     , Rafael J. Wysocki wrote:
> If you know of any other unresolved regressions from 2.6.33, 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.

Please list these two similar regressions from 2.6.33 in the r600 DRM:

 * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer:
           https://bugs.freedesktop.org/show_bug.cgi?id=27571

 * r600 CS checker rejects narrow FBO renderbuffers:
           https://bugs.freedesktop.org/show_bug.cgi?id=27609

Thanks.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Ben Gamari]

On Tue, 20 Apr 2010 05:15:57 +0200 (CEST), "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message contains a list of some regressions from 2.6.33,
> 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 regressions from 2.6.33, 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.
> 

I have recently reported this suspend regression on my Dell laptop hardware.

References: http://lkml.org/lkml/2010/4/18/20
Bug-report: https://bugzilla.kernel.org/show_bug.cgi?id=15820

Thanks,

- Ben

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Ben Gamari]

On Tue, 20 Apr 2010 05:15:57 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> This message contains a list of some regressions from 2.6.33,
> 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 regressions from 2.6.33, 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.
> 

I have recently reported this suspend regression on my Dell laptop hardware.

References: http://lkml.org/lkml/2010/4/18/20
Bug-report: https://bugzilla.kernel.org/show_bug.cgi?id=15820

Thanks,

- Ben

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Ben Gamari wrote:
> On Tue, 20 Apr 2010 05:15:57 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > This message contains a list of some regressions from 2.6.33,
> > 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 regressions from 2.6.33, 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.
> > 
> 
> I have recently reported this suspend regression on my Dell laptop hardware.
> 
> References: http://lkml.org/lkml/2010/4/18/20
> Bug-report: https://bugzilla.kernel.org/show_bug.cgi?id=15820

This has been added to the list now.  Please check my comment in the Bugzilla
entry.

Rafael

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Rafael J. Wysocki]

On Wednesday 21 April 2010, Ben Gamari wrote:
> On Tue, 20 Apr 2010 05:15:57 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > This message contains a list of some regressions from 2.6.33,
> > 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 regressions from 2.6.33, 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.
> > 
> 
> I have recently reported this suspend regression on my Dell laptop hardware.
> 
> References: http://lkml.org/lkml/2010/4/18/20
> Bug-report: https://bugzilla.kernel.org/show_bug.cgi?id=15820

This has been added to the list now.  Please check my comment in the Bugzilla
entry.

Rafael

Re: 2.6.34-rc5: Reported regressions from 2.6.33

[Ben Gamari]

On Tue, 20 Apr 2010 05:15:57 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> This message contains a list of some regressions from 2.6.33,
> 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 regressions from 2.6.33, 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.
> 

I have recently reported this suspend regression on my Dell laptop hardware.

References: http://lkml.org/lkml/2010/4/18/20
Bug-report: https://bugzilla.kernel.org/show_bug.cgi?id=15820

Thanks,

- Ben

2.6.35-rc3: Reported regressions 2.6.33 -> 2.6.34

[Rafael J. Wysocki]

This message contains a list of some post-2.6.33 regressions introduced before
2.6.34, 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.33 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
  ----------------------------------------
  2010-06-21      114       36          28
  2010-06-13      111       40          34
  2010-05-09       80       27          24
  2010-05-04       76       26          22
  2010-04-20       64       35          34
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16254
Subject		: TCP stream performance regression due to c377411f2494a931ff7facdbb3a6839b1266bcf6
Submitter	: Alex,Shi <alex.shi@intel.com>
Date		: 2010-06-18 7:17 (3 days old)
First-Bad-Commit: http://git.kernel.org/linus/c377411f2494a931ff7facdbb3a6839b1266bcf6
Message-ID	: <1276845448.2118.346.camel@debian>
References	: http://marc.info/?l=linux-kernel&m=127684931020672&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16233
Subject		: Fwd: [2.6.34] INFO: task rsync:20019 blocked for more than 120 seconds.
Submitter	: Jan De Luyck <mailinglists+linuxkernel_20080830@kcore.org>
Date		: 2010-06-14 19:49 (7 days old)
Message-ID	: <AANLkTimutyh3WIALv3NIxA8Xt5JtU6tp4EWOnuSqhdyD@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127654498016377&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16207
Subject		: Suspend hangs since 2.6.34
Submitter	: Tino Keitel <tino.keitel+xorg@tikei.de>
Date		: 2010-06-09 17:53 (12 days old)
Message-ID	: <20100609175356.GA17332@x61.home>
References	: http://marc.info/?l=linux-kernel&m=127610606214060&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16206
Subject		: PROBLEM: PPP and other serial port related application hangs in kernel space
Submitter	: Ales Teska <ales.teska@gmail.com>
Date		: 2010-06-09 20:46 (12 days old)
Message-ID	: <900E3B14-5B92-4A37-9581-049DB40F4D1C@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127611640301071&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16170
Subject		: Leadtek Winfast DTV Dongle (STK7700P based) is not working in 2.6.34
Submitter	:  <macjariel@gmail.com>
Date		: 2010-06-09 11:11 (12 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16162
Subject		: SSD + sata_nv + btrfs oops
Submitter	: Dave Airlie <airlied@gmail.com>
Date		: 2010-06-01 3:04 (20 days old)
Message-ID	: <AANLkTilqsIdlzZgUf7TMLHYKqHDZoVkcs42vcG8wXKEr@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127536149022333&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16158
Subject		: winxp guest hangs after idle for ~30 minutes
Submitter	:  <brimhall@pobox.com>
Date		: 2010-06-08 17:52 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16139
Subject		: wait_even_interruptible_timeout(), signal, spin_lock() = system hang
Submitter	: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Date		: 2010-05-28 16:44 (24 days old)
Message-ID	: <AANLkTiliRFydAhxH2-Dp1RKuz6sq7vgWIcMvLMi68ftg@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127506510328758&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16137
Subject		: Ooops in BTRFS in 2.6.34 / x86_64 when mounting subvolume by name
Submitter	: armin walland <a.walland@focusmr.com>
Date		: 2010-05-27 12:27 (25 days old)
Message-ID	: <201005271428.01239.a.walland@focusmr.com>
References	: http://marc.info/?l=linux-kernel&m=127496434110736&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16135
Subject		: [BUG] kacpi_notify goes into an infinite loop (luckly it calls cond_resched)
Submitter	: Steven Rostedt <rostedt@goodmis.org>
Date		: 2010-05-29 1:01 (23 days old)
First-Bad-Commit: http://git.kernel.org/linus/fa80945269f312bc609e8384302f58b03c916e12
Message-ID	: <1275094882.22648.607.camel@gandalf.stny.rr.com>
References	: http://marc.info/?l=linux-kernel&m=127509490405845&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16111
Subject		: hostap_pci: infinite registered netdevice wifi0
Submitter	: Petr Pisar <petr.pisar@atlas.cz>
Date		: 2010-06-02 20:55 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16097
Subject		: 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated"
Submitter	: Harald Dunkel <harald.dunkel@aixigo.de>
Date		: 2010-05-25 9:12 (27 days old)
Message-ID	: <4BFB947E.9080509@aixigo.de>
References	: http://marc.info/?l=linux-kernel&m=127477877432254&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16084
Subject		: iwl3945 bug in 2.6.34
Submitter	: Satish Eerpini <eerpini@gmail.com>
Date		: 2010-05-23 6:37 (29 days old)
Message-ID	: <AANLkTik_7rxDBc0TKlAfoYyM5S6Cf_Hyxbr4W5ORnTsq@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127459596015626&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16082
Subject		: host panic on kernel 2.6.34
Submitter	: Hao, Xudong <xudong.hao@intel.com>
Date		: 2010-05-24 8:23 (28 days old)
Message-ID	: <BC00F5384FCFC9499AF06F92E8B78A9E04DCCCE242@shsmsx502.ccr.corp.intel.com>
References	: http://marc.info/?l=linux-kernel&m=127468951208864&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16050
Subject		: The ibmcam driver is not working
Submitter	: Bill Davidsen <davidsen@tmr.com>
Date		: 2010-05-25 23:02 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16035
Subject		: Incorrect initial resolution of (external) vga monitor with KMS
Submitter	:  <andreas.eckstein@gmx.net>
Date		: 2010-05-23 12:28 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16034
Subject		: 2.6.34: dlm: possible circular locking dependency detected
Submitter	: CaT <cat@zip.com.au>
Date		: 2010-05-21 6:59 (31 days old)
Message-ID	: <20100521065933.GH2657@zip.com.au>
References	: http://marc.info/?l=linux-kernel&m=127442519608471&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15977
Subject		: WARNING: at lib/dma-debug.c:866 check_for_stack
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-05-14 8:56 (38 days old)
Message-ID	: <AANLkTikyx2eaxaiUCFDSfpmn1UG0t2GOxArz6F4wp1LJ@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127382742729825&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15936
Subject		: Suspicious rcu_dereference_check() usage detected during 2.6.34-rc6 boot on PPC64/p5 processor
Submitter	: Subrata Modak <subrata@linux.vnet.ibm.com>
Date		: 2010-05-06 7:29 (46 days old)
Message-ID	: <1273130279.4898.5.camel@subratamodak.linux.ibm.com>
References	: http://marc.info/?l=linux-kernel&m=127313031922395&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15924
Subject		: kacpid consumes ~100% CPU, system freezes randomly
Submitter	: Jaroslav Kameník <jaroslav@kamenik.cz>
Date		: 2010-05-06 21:12 (46 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15862
Subject		: 2.6.34-rc4/5: iwlagn unusable until reload
Submitter	: Nico Schottelius <nico-linux-20100427@schottelius.org>
Date		: 2010-04-27 7:49 (55 days old)
Message-ID	: <20100427074934.GB3261@ikn.schottelius.org>
References	: http://marc.info/?l=linux-kernel&m=127235784004839&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2010-04-15 21:02 (67 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2
Handled-By	: Frederic Weisbecker <fweisbec@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 20:14 (99 days old)
Message-ID	: <20100314201434.GE22059@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date		: 2010-03-31 10:21 (82 days old)
Message-ID	: <20100331102142.GA3294@swordfish.minsk.epam.com>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-03-28 11:31 (85 days old)
Message-ID	: <1269775909.5301.4.camel@localhost.localdomain>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2010-03-27 16:11 (86 days old)
Message-ID	: <20100327161104.GA12043@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2
Handled-By	: Jesse Barnes <jbarnes@virtuousgeek.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-03-08 1:26 (105 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date		: 2010-04-01 01:09 (81 days old)


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16147
Subject		: ksoftirq hogs the CPU
Submitter	: Thomas Jarosch <thomas.jarosch@intra2net.com>
Date		: 2010-06-07 15:17 (14 days old)
First-Bad-Commit: http://git.kernel.org/linus/ae74e823cb7d4cd476f623fce9a38f625f6c09a8
Handled-By	: Martin Wilck <martin.wilck@ts.fujitsu.com>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=26732


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16138
Subject		: PCMCIA regression
Submitter	: Mikulas Patocka <mpatocka@redhat.com>
Date		: 2010-05-25 20:25 (27 days old)
Message-ID	: <Pine.LNX.4.64.1005251619020.12278@hs20-bc2-1.build.redhat.com>
References	: http://marc.info/?l=linux-kernel&m=127481913909672&w=2
Handled-By	: Dominik Brodowski <linux@brodo.de>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=26685


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16054
Subject		: UML broken for CONFIG_SLAB
Submitter	: Parag Warudkar <parag.lkml@gmail.com>
Date		: 2010-05-23 21:40 (29 days old)
Message-ID	: <alpine.DEB.2.00.1005231149100.605@parag-laptop>
References	: http://marc.info/?l=linux-kernel&m=127465083806617&w=2
Handled-By	: Borislav Petkov <bp@alien8.de>
Patch		: http://git.kernel.org/tip/055c47272b8f5679d08ccc57efea3cb4aaeb5fc6


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16040
Subject		: kacpid consumes ~40% of cpu all the time beginning with 2.6.34
Submitter	: Mehmet Giritli <mehmet@giritli.eu>
Date		: 2010-05-24 07:32 (28 days old)
Patch		: https://patchwork.kernel.org/patch/104903/
		  https://patchwork.kernel.org/patch/104912/
		  https://patchwork.kernel.org/patch/104909/
		  https://patchwork.kernel.org/patch/104911/
		  https://patchwork.kernel.org/patch/104910/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16007
Subject		: x86/pci Oops with CONFIG_SND_HDA_INTEL
Submitter	: Graham Ramsey <ramsey.graham@ntlworld.com>
Date		: 2010-05-19 17:09 (33 days old)
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: https://patchwork.kernel.org/patch/105662/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15951
Subject		: commit 9630bdd9 changes behavior of the poweroff
Submitter	: Michal Hocko <mhocko@suse.cz>
Date		: 2010-04-01 13:39 (81 days old)
First-Bad-Commit: http://git.kernel.org/linus/9630bdd9b15d2f489c646d8bc04b60e53eb5ec78
Message-ID	: <20100401133923.GA4104@tiehlicka.suse.cz>
References	: http://marc.info/?l=linux-kernel&m=127012918316305&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>
Patch		: https://patchwork.kernel.org/patch/106701/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15863
Subject		: 2.6.34-rc5-git7 (plus all patches) -- another suspicious rcu_dereference_check() usage.
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-04-27 0:51 (55 days old)
Message-ID	: <h2ya44ae5cd1004261751waa5cb65ei3d139cbcfa2cc5cf@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127232949104878&w=2
Handled-By	: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Patch		: https://patchwork.kernel.org/patch/96096/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (100 days old)
Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
Handled-By	: Michael Ellerman <michael@ellerman.id.au>
		  Jindřich Makovička <makovick@gmail.com>
Patch		: http://patchwork.ozlabs.org/patch/52978/
		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html


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

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

Please let the tracking teak 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-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (100 days old)
Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
Handled-By	: Michael Ellerman <michael-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
		  Jindřich Makovička <makovick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://patchwork.ozlabs.org/patch/52978/
		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (100 days old)
Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
Handled-By	: Michael Ellerman <michael@ellerman.id.au>
		  Jindřich Makovička <makovick@gmail.com>
Patch		: http://patchwork.ozlabs.org/patch/52978/
		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Stefan Lippers-Hollmann]

[-- Attachment #1: Type: Text/Plain, Size: 1155 bytes --]

Hi

On Tuesday 22 June 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 and 2.6.34.  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=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (100 days old)
> Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> Handled-By	: Michael Ellerman <michael@ellerman.id.au>
> 		  Jindřich Makovička <makovick@gmail.com>
> Patch		: http://patchwork.ozlabs.org/patch/52978/
> 		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html

At least the effects on b2c2-flexcop-pci are still valid, in linux-2.6
HEAD and linux-next (next-20100621).

Regards
	Stefan Lippers-Hollmann

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Tuesday, June 22, 2010, Stefan Lippers-Hollmann wrote:
> Hi
> 
> On Tuesday 22 June 2010, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.33 and 2.6.34.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.33 and 2.6.34.  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=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> > Date		: 2010-03-13 23:53 (100 days old)
> > Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> > Handled-By	: Michael Ellerman <michael-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
> > 		  Jindøich Makovièka <makovick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Patch		: http://patchwork.ozlabs.org/patch/52978/
> > 		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
> 
> At least the effects on b2c2-flexcop-pci are still valid, in linux-2.6
> HEAD and linux-next (next-20100621).

Thanks for the update.

Rafael

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Tuesday, June 22, 2010, Stefan Lippers-Hollmann wrote:
> Hi
> 
> On Tuesday 22 June 2010, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.33 and 2.6.34.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.33 and 2.6.34.  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=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists@nerdbynature.de>
> > Date		: 2010-03-13 23:53 (100 days old)
> > Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> > Handled-By	: Michael Ellerman <michael@ellerman.id.au>
> > 		  Jindřich Makovička <makovick@gmail.com>
> > Patch		: http://patchwork.ozlabs.org/patch/52978/
> > 		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
> 
> At least the effects on b2c2-flexcop-pci are still valid, in linux-2.6
> HEAD and linux-next (next-20100621).

Thanks for the update.

Rafael

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

Sorry for the late reply:

On Mon, 21 Jun 2010 at 00:32, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 and 2.6.34.  Please verify if it still should
> be listed and let the tracking team know (either way).

Yes, the bug is still present in 2.6.34 and .35-rc3, but a tested patch is 
available, hopefully to be included in 2.6.35.

Thanks,
Christian.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (100 days old)
> Message-ID	: < <AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> Handled-By	: Michael Ellerman <michael@ellerman.id.au>
> 		  Jindřich Makovička <makovick@gmail.com>
> Patch		: http://patchwork.ozlabs.org/patch/52978/
> 		  http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
-- 
BOFH excuse #302:

microelectronic Riemannian curved-space fault in write-only file system

2.6.35-rc3: Reported regressions 2.6.33 -> 2.6.34

[Rafael J. Wysocki]

[NOTES:
 * This report has been delayed, because I had to go through all of the
   entries and filter out the fixed ones, invalid ones etc.  Of course, I might
   have missed some, but hopefully not too many.
 * E-mail reports from the last 7 days are not included.]

This message contains a list of some post-2.6.33 regressions introduced before
2.6.34, 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.33 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
  ----------------------------------------
  2010-06-13      111       40          34
  2010-05-09       80       27          24
  2010-05-04       76       26          22
  2010-04-20       64       35          34
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16170
Subject		: Leadtek Winfast DTV Dongle (STK7700P based) is not working in 2.6.34
Submitter	: macjariel <macjariel@gmail.com>
Date		: 2010-06-09 11:11 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16162
Subject		: SSD + sata_nv + btrfs oops
Submitter	: Dave Airlie <airlied@gmail.com>
Date		: 2010-06-01 3:04 (13 days old)
Message-ID	: <AANLkTilqsIdlzZgUf7TMLHYKqHDZoVkcs42vcG8wXKEr@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127536149022333&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16158
Subject		: winxp guest hangs after idle for ~30 minutes
Submitter	: brimhall <brimhall@pobox.com>
Date		: 2010-06-08 17:52 (6 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16139
Subject		: wait_even_interruptible_timeout(), signal, spin_lock() = system hang
Submitter	: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Date		: 2010-05-28 16:44 (17 days old)
Message-ID	: <AANLkTiliRFydAhxH2-Dp1RKuz6sq7vgWIcMvLMi68ftg@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127506510328758&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16137
Subject		: Ooops in BTRFS in 2.6.34 / x86_64 when mounting subvolume by name
Submitter	: armin walland <a.walland@focusmr.com>
Date		: 2010-05-27 12:27 (18 days old)
Message-ID	: <201005271428.01239.a.walland@focusmr.com>
References	: http://marc.info/?l=linux-kernel&m=127496434110736&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16136
Subject		: Linux 2.6.34 causes system lockup on Compaq Presario 2200 Laptop
Submitter	: Jeffrey Merkey <jeffmerkey@gmail.com>
Date		: 2010-05-27 18:08 (18 days old)
Message-ID	: <AANLkTil6GGSoc8TpzRacr1LZBZS3ee3H1ejYDSqfdul4@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127498375415689&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16135
Subject		: [BUG] kacpi_notify goes into an infinite loop (luckly it calls cond_resched)
Submitter	: Steven Rostedt <rostedt@goodmis.org>
Date		: 2010-05-29 1:01 (16 days old)
First-Bad-Commit: http://git.kernel.org/linus/fa80945269f312bc609e8384302f58b03c916e12
Message-ID	: <1275094882.22648.607.camel@gandalf.stny.rr.com>
References	: http://marc.info/?l=linux-kernel&m=127509490405845&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16134
Subject		: 2.6.34 hard lock ppp/do_tty_hangup, regression
Submitter	: Richard Zidlicky <rz@linux-m68k.org>
Date		: 2010-05-26 8:48 (19 days old)
Message-ID	: <20100526084811.GA5890@linux-m68k.org>
References	: http://marc.info/?l=linux-kernel&m=127486354023473&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16111
Subject		: hostap_pci: infinite registered netdevice wifi0
Submitter	: Petr Pisar <petr.pisar@atlas.cz>
Date		: 2010-06-02 20:55 (12 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16097
Subject		: 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated"
Submitter	: Harald Dunkel <harald.dunkel@aixigo.de>
Date		: 2010-05-25 9:12 (20 days old)
Message-ID	: <4BFB947E.9080509@aixigo.de>
References	: http://marc.info/?l=linux-kernel&m=127477877432254&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16084
Subject		: iwl3945 bug in 2.6.34
Submitter	: Satish Eerpini <eerpini@gmail.com>
Date		: 2010-05-23 6:37 (22 days old)
Message-ID	: <AANLkTik_7rxDBc0TKlAfoYyM5S6Cf_Hyxbr4W5ORnTsq@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127459596015626&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16082
Subject		: host panic on kernel 2.6.34
Submitter	: Hao, Xudong <xudong.hao@intel.com>
Date		: 2010-05-24 8:23 (21 days old)
Message-ID	: <BC00F5384FCFC9499AF06F92E8B78A9E04DCCCE242@shsmsx502.ccr.corp.intel.com>
References	: http://marc.info/?l=linux-kernel&m=127468951208864&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16054
Subject		: UML broken for CONFIG_SLAB
Submitter	: Parag Warudkar <parag.lkml@gmail.com>
Date		: 2010-05-23 21:40 (22 days old)
Message-ID	: <alpine.DEB.2.00.1005231149100.605@parag-laptop>
References	: http://marc.info/?l=linux-kernel&m=127465083806617&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16050
Subject		: The ibmcam driver is not working
Submitter	: Bill Davidsen <davidsen@tmr.com>
Date		: 2010-05-25 23:02 (20 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16040
Subject		: kacpid consumes ~40% of cpu all the time beginning with 2.6.34
Submitter	: Mehmet Giritli <mehmet@giritli.eu>
Date		: 2010-05-24 07:32 (21 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16035
Subject		: Incorrect initial resolution of (external) vga monitor with KMS
Submitter	: andreas.eckstein <andreas.eckstein@gmx.net>
Date		: 2010-05-23 12:28 (22 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16034
Subject		: 2.6.34: dlm: possible circular locking dependency detected
Submitter	: CaT <cat@zip.com.au>
Date		: 2010-05-21 6:59 (24 days old)
Message-ID	: <20100521065933.GH2657@zip.com.au>
References	: http://marc.info/?l=linux-kernel&m=127442519608471&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15977
Subject		: WARNING: at lib/dma-debug.c:866 check_for_stack
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-05-14 8:56 (31 days old)
Message-ID	: <AANLkTikyx2eaxaiUCFDSfpmn1UG0t2GOxArz6F4wp1LJ@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127382742729825&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15970
Subject		: BUG: amd64-agp (2.6.34-rc7)
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-05-11 20:56 (34 days old)
Message-ID	: <4BE9C469.2020901@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=127361149610881&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15951
Subject		: commit 9630bdd9 changes behavior of the poweroff
Submitter	: Michal Hocko <mhocko@suse.cz>
Date		: 2010-04-01 13:39 (74 days old)
First-Bad-Commit: http://git.kernel.org/linus/9630bdd9b15d2f489c646d8bc04b60e53eb5ec78
Message-ID	: <20100401133923.GA4104@tiehlicka.suse.cz>
References	: http://marc.info/?l=linux-kernel&m=127012918316305&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15936
Subject		: Suspicious rcu_dereference_check() usage detected during 2.6.34-rc6 boot on PPC64/p5 processor
Submitter	: Subrata Modak <subrata@linux.vnet.ibm.com>
Date		: 2010-05-06 7:29 (39 days old)
Message-ID	: <1273130279.4898.5.camel@subratamodak.linux.ibm.com>
References	: http://marc.info/?l=linux-kernel&m=127313031922395&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15924
Subject		: kacpid consumes ~100% CPU, system freezes randomly
Submitter	: Jaroslav Kameník <jaroslav@kamenik.cz>
Date		: 2010-05-06 21:12 (39 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15862
Subject		: 2.6.34-rc4/5: iwlagn unusable until reload
Submitter	: Nico Schottelius <nico-linux-20100427@schottelius.org>
Date		: 2010-04-27 7:49 (48 days old)
Message-ID	: <20100427074934.GB3261@ikn.schottelius.org>
References	: http://marc.info/?l=linux-kernel&m=127235784004839&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15858
Subject		: [2.6.34-rc5] bad page state copying to/from HFS+ filesystem...
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2010-04-25 21:14 (50 days old)
Message-ID	: <v2k6278d2221004251414kbbcc41baw78b86120d81dce7d@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127223008621881&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2010-04-15 21:02 (60 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2
Handled-By	: Frederic Weisbecker <fweisbec@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 20:14 (92 days old)
Message-ID	: <20100314201434.GE22059@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi@intel.com>
Date		: 2010-03-25 8:40 (81 days old)
First-Bad-Commit: http://git.kernel.org/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel@alexs-hp.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl@linux-foundation.org>
		  Pekka Enberg <penberg@cs.helsinki.fi>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-04-01 6:06 (74 days old)
Message-ID	: <20100401060624.GA1329@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2
Handled-By	: Eric Miao <eric.y.miao@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date		: 2010-03-31 10:21 (75 days old)
Message-ID	: <20100331102142.GA3294@swordfish.minsk.epam.com>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-03-28 11:31 (78 days old)
Message-ID	: <1269775909.5301.4.camel@localhost.localdomain>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2010-03-27 16:11 (79 days old)
Message-ID	: <20100327161104.GA12043@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2
Handled-By	: Jesse Barnes <jbarnes@virtuousgeek.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-03-08 1:26 (98 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date		: 2010-04-01 01:09 (74 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2010-03-25 20:04 (81 days old)
Message-ID	: <201003252104.24965.maciej.rutecki@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2
Handled-By	: Chris Wilson <chris@chris-wilson.co.uk>


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16147
Subject		: ksoftirq hogs the CPU
Submitter	: Thomas Jarosch <thomas.jarosch@intra2net.com>
Date		: 2010-06-07 15:17 (7 days old)
First-Bad-Commit: http://git.kernel.org/linus/ae74e823cb7d4cd476f623fce9a38f625f6c09a8
Handled-By	: Martin Wilck <martin.wilck@ts.fujitsu.com>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=26732


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16138
Subject		: PCMCIA regression
Submitter	: Mikulas Patocka <mpatocka@redhat.com>
Date		: 2010-05-25 20:25 (20 days old)
Message-ID	: <Pine.LNX.4.64.1005251619020.12278@hs20-bc2-1.build.redhat.com>
References	: http://marc.info/?l=linux-kernel&m=127481913909672&w=2
Handled-By	: Dominik Brodowski <linux@brodo.de>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=26685


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16007
Subject		: x86/pci Oops with CONFIG_SND_HDA_INTEL
Submitter	: Graham Ramsey <ramsey.graham@ntlworld.com>
Date		: 2010-05-19 17:09 (26 days old)
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: https://patchwork.kernel.org/patch/105662/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15909
Subject		: open("a/",O_NOFOLLOW) fails with ELOOP if "a" is a symbolic link to a directory.
Submitter	: Marius Tolzmann <tolzmann@molgen.mpg.de>
Date		: 2010-05-05 13:01 (40 days old)
Handled-By	: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
		  Jan Kara <jack@suse.cz>
Patch		: https://patchwork.kernel.org/patch/99291/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15863
Subject		: 2.6.34-rc5-git7 (plus all patches) -- another suspicious rcu_dereference_check() usage.
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-04-27 0:51 (48 days old)
Message-ID	: <h2ya44ae5cd1004261751waa5cb65ei3d139cbcfa2cc5cf@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127232949104878&w=2
Handled-By	: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Patch		: https://patchwork.kernel.org/patch/96096/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (93 days old)
Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
Handled-By	: Michael Ellerman <michael@ellerman.id.au>
Patch		: http://patchwork.ozlabs.org/patch/52978/


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

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

Please let the tracking teak 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-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (93 days old)
Message-ID	: <<alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
Handled-By	: Michael Ellerman <michael-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
Patch		: http://patchwork.ozlabs.org/patch/52978/

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (93 days old)
Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
Handled-By	: Michael Ellerman <michael@ellerman.id.au>
Patch		: http://patchwork.ozlabs.org/patch/52978/

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Stefan Lippers-Hollmann]

Hi

On Sunday 13 June 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 and 2.6.34.  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=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> Date		: 2010-03-13 23:53 (93 days old)
> Message-ID	: <<alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> Handled-By	: Michael Ellerman <michael-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
> Patch		: http://patchwork.ozlabs.org/patch/52978/

Still existing in 2.6.34 and 2.6.35 HEAD, however a patch fixing the issue 
for b2c2-flexcop/ flexcop-pci has been posted last week:
	From:		Jindřich Makovička <makovick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
	Subject:		[PATCH] DVB flexcop-pci: sanitize driver name to avoid warning on load
	Date:		Mon, 7 Jun 2010 14:51:30 +0200
	Message-ID:	<AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh-JsoAwUIsXotQFR93xxRIaA@public.gmane.orgcom>
	URL:			http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html

Regards
	Stefan Lippers-Hollmann

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Stefan Lippers-Hollmann]

Hi

On Sunday 13 June 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 and 2.6.34.  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=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (93 days old)
> Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> Handled-By	: Michael Ellerman <michael@ellerman.id.au>
> Patch		: http://patchwork.ozlabs.org/patch/52978/

Still existing in 2.6.34 and 2.6.35 HEAD, however a patch fixing the issue 
for b2c2-flexcop/ flexcop-pci has been posted last week:
	From:		Jindřich Makovička <makovick@gmail.com>
	Subject:		[PATCH] DVB flexcop-pci: sanitize driver name to avoid warning on load
	Date:		Mon, 7 Jun 2010 14:51:30 +0200
	Message-ID:	<AANLkTikNcCtUn9SQwKu2b3IE6NiAwAhciHsm1HVH4EJh@mail.gmail.com>
	URL:			http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html

Regards
	Stefan Lippers-Hollmann

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Sun, 13 Jun 2010 at 17:22, Stefan Lippers-Hollmann wrote:
> Still existing in 2.6.34 and 2.6.35 HEAD, however a patch fixing the issue 
> for b2c2-flexcop/ flexcop-pci has been posted last week:

So, now we have two patches for slightly different issues?

* http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
  ...fixes the flexcop-pci.c driver.

* http://patchwork.ozlabs.org/patch/52978/
  ...fixes "some bogus firmwares include properties with "/" in their
  name". I'm not sure if this would make the flexcop-pci.c badness go 
  away too. 

Anyway, both patches are not upstream yet, but Michael mentioned that 
Grant Likely or Ben might push it eventually.

Thanks,
Christian.
-- 
BOFH excuse #363:

Out of cards on drive D:

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Sun, 13 Jun 2010 at 17:22, Stefan Lippers-Hollmann wrote:
> Still existing in 2.6.34 and 2.6.35 HEAD, however a patch fixing the issue 
> for b2c2-flexcop/ flexcop-pci has been posted last week:

So, now we have two patches for slightly different issues?

* http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
  ...fixes the flexcop-pci.c driver.

* http://patchwork.ozlabs.org/patch/52978/
  ...fixes "some bogus firmwares include properties with "/" in their
  name". I'm not sure if this would make the flexcop-pci.c badness go 
  away too. 

Anyway, both patches are not upstream yet, but Michael mentioned that 
Grant Likely or Ben might push it eventually.

Thanks,
Christian.
-- 
BOFH excuse #363:

Out of cards on drive D:

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Grant Likely]

On Sun, Jun 13, 2010 at 12:10 PM, Christian Kujau <lists@nerdbynature.de> wrote:
> On Sun, 13 Jun 2010 at 17:22, Stefan Lippers-Hollmann wrote:
>> Still existing in 2.6.34 and 2.6.35 HEAD, however a patch fixing the issue
>> for b2c2-flexcop/ flexcop-pci has been posted last week:
>
> So, now we have two patches for slightly different issues?
>
> * http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
>  ...fixes the flexcop-pci.c driver.
>
> * http://patchwork.ozlabs.org/patch/52978/
>  ...fixes "some bogus firmwares include properties with "/" in their
>  name". I'm not sure if this would make the flexcop-pci.c badness go
>  away too.
>
> Anyway, both patches are not upstream yet, but Michael mentioned that
> Grant Likely or Ben might push it eventually.

On brief review, they look like completely different issues.  I doubt
the second patch will fix the flexcop-pci issue.  I'll pick up the
device tree patch, but the flexcop-pci patch should go in by the
v4l/dvb tree.

g.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Grant Likely]

On Sun, Jun 13, 2010 at 12:10 PM, Christian Kujau <lists@nerdbynature.de> wrote:
> On Sun, 13 Jun 2010 at 17:22, Stefan Lippers-Hollmann wrote:
>> Still existing in 2.6.34 and 2.6.35 HEAD, however a patch fixing the issue
>> for b2c2-flexcop/ flexcop-pci has been posted last week:
>
> So, now we have two patches for slightly different issues?
>
> * http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/00137.html
>  ...fixes the flexcop-pci.c driver.
>
> * http://patchwork.ozlabs.org/patch/52978/
>  ...fixes "some bogus firmwares include properties with "/" in their
>  name". I'm not sure if this would make the flexcop-pci.c badness go
>  away too.
>
> Anyway, both patches are not upstream yet, but Michael mentioned that
> Grant Likely or Ben might push it eventually.

On brief review, they look like completely different issues.  I doubt
the second patch will fix the flexcop-pci issue.  I'll pick up the
device tree patch, but the flexcop-pci patch should go in by the
v4l/dvb tree.

g.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
> On brief review, they look like completely different issues.  I doubt
> the second patch will fix the flexcop-pci issue.

It will, see how name wht slashes propagated by request_irq()

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Alexey Dobriyan]

On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
> On brief review, they look like completely different issues.  I doubt
> the second patch will fix the flexcop-pci issue.

It will, see how name wht slashes propagated by request_irq()

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Jindrich Makovicka]

On Mon, 14 Jun 2010 09:39:48 +0300
Alexey Dobriyan <adobriyan@gmail.com>
wrote:

> On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
> > On brief review, they look like completely different issues.  I
> > doubt the second patch will fix the flexcop-pci issue.
> 
> It will, see how name wht slashes propagated by request_irq()

Yes, the latter patch dodges the issue with flexcop driver by simply
skipping the directory creation, but both patches should be applied IMO.
The former to fix the flexcop driver because we can trivially fix it,
the latter to solve problems with any generic bogus firmware.

-- 
Jindrich Makovicka

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Jindrich Makovicka]

On Mon, 14 Jun 2010 09:39:48 +0300
Alexey Dobriyan <adobriyan@gmail.com>
wrote:

> On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
> > On brief review, they look like completely different issues.  I
> > doubt the second patch will fix the flexcop-pci issue.
> 
> It will, see how name wht slashes propagated by request_irq()

Yes, the latter patch dodges the issue with flexcop driver by simply
skipping the directory creation, but both patches should be applied IMO.
The former to fix the flexcop driver because we can trivially fix it,
the latter to solve problems with any generic bogus firmware.

-- 
Jindrich Makovicka

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Grant Likely]

On Mon, Jun 14, 2010 at 12:39 AM, Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
>> On brief review, they look like completely different issues.  I doubt
>> the second patch will fix the flexcop-pci issue.
>
> It will, see how name wht slashes propagated by request_irq()

I think we've crossed wires.  By second patch I mean the patch that
changes OF code.  That change has absolutely no bearing on the
flexcop-pci driver.  The patch to the flexcop-pci driver looks correct
to me, but it is completely unrelated to the OF badness.

g.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Grant Likely]

On Mon, Jun 14, 2010 at 12:39 AM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
>> On brief review, they look like completely different issues.  I doubt
>> the second patch will fix the flexcop-pci issue.
>
> It will, see how name wht slashes propagated by request_irq()

I think we've crossed wires.  By second patch I mean the patch that
changes OF code.  That change has absolutely no bearing on the
flexcop-pci driver.  The patch to the flexcop-pci driver looks correct
to me, but it is completely unrelated to the OF badness.

g.

2.6.34-rc6-git6: Reported regressions from 2.6.33

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.33,
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 regressions from 2.6.33, 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
  ----------------------------------------
  2010-05-09       80       27          24
  2010-05-04       76       26          22
  2010-04-20       64       35          34
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15951
Subject		: commit 9630bdd9 changes behavior of the poweroff
Submitter	: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
Date		: 2010-04-01 13:39 (39 days old)
Message-ID	: <20100401133923.GA4104-VqjxzfR4DlwKmadIfiO5sKVXKuFTiq87@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127012918316305&w=4
Handled-By	: Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15936
Subject		: Suspicious rcu_dereference_check() usage detected during 2.6.34-rc6 boot on PPC64/p5 processor
Submitter	: Subrata Modak <subrata-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date		: 2010-05-06 7:29 (4 days old)
Message-ID	: <1273130279.4898.5.camel-NRFfyExJdYpgXGGE5LP+UZlqa2bBAFbm0E9HWUfgJXw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127313031922395&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15935
Subject		: [BUG] btrfs: report a direct-IO bug
Submitter	: liubo <liubo2009-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Date		: 2010-05-06 1:47 (4 days old)
Message-ID	: <4BE21FC1.1010901-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127311036803487&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15924
Subject		: kacpid consumes ~100% CPU, system freezes randomly
Submitter	: Jaroslav Kameník <jaroslav-FZZqD5xcwZ7rBKCeMvbIDA@public.gmane.org>
Date		: 2010-05-06 21:12 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15909
Subject		: open("a/",O_NOFOLLOW) fails with ELOOP if "a" is a symbolic link to a directory.
Submitter	: Marius Tolzmann <tolzmann-KUpvgZVWgV9o1qOY/usvUg@public.gmane.org>
Date		: 2010-05-05 13:01 (5 days old)
Handled-By	: OGAWA Hirofumi <hirofumi-UIVanBePwB70ZhReMnHkpc8NsWr+9BEh@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15880
Subject		: Very bad regression from 2.6.33 as of 1600f9def
Submitter	: Alex Elsayed <eternaleye-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-29 2:28 (11 days old)
Message-ID	: <loom.20100429T041908-663-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127250825306178&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15863
Subject		: 2.6.34-rc5-git7 (plus all patches) -- another suspicious rcu_dereference_check() usage.
Submitter	: Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-27 0:51 (13 days old)
Message-ID	: <h2ya44ae5cd1004261751waa5cb65ei3d139cbcfa2cc5cf-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>
References	: http://marc.info/?l=linux-kernel&m=127232949104878&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15862
Subject		: 2.6.34-rc4/5: iwlagn unusable until reload
Submitter	: Nico Schottelius <nico-linux-20100427-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Date		: 2010-04-27 7:49 (13 days old)
Message-ID	: <20100427074934.GB3261-9ll+q7fL1vOwdVNcq5OhcUB+6BGkLq7r@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127235784004839&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15858
Subject		: [2.6.34-rc5] bad page state copying to/from HFS+ filesystem...
Submitter	: Daniel J Blueman <daniel.blueman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-25 21:14 (15 days old)
Message-ID	: <v2k6278d2221004251414kbbcc41baw78b86120d81dce7d-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>
References	: http://marc.info/?l=linux-kernel&m=127223008621881&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-04-15 21:02 (25 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb-JsoAwUIsXov1KXRcyAk9cg@public.gmane.orgl.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15788
Subject		: external usb sound card doesn't work after resume
Submitter	: François Valenduc <francois.valenduc-bmtTS95sd5BUM80lpFwj4w@public.gmane.org>
Date		: 2010-04-15 10:16 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-14 20:14 (57 days old)
Message-ID	: <20100314201434.GE22059-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-25 8:40 (46 days old)
First-Bad-Commit: http://git.kernel.org/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel-c8rhgrCDLIED0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
		  Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-04-01 6:06 (39 days old)
Message-ID	: <20100401060624.GA1329-+ZI9xUNit7I@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-31 10:21 (40 days old)
Message-ID	: <<<20100331102142.GA3294-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Date		: 2010-03-28 11:31 (43 days old)
Message-ID	: <1269775909.5301.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
Date		: 2010-03-27 16:11 (44 days old)
Message-ID	: <20100327161104.GA12043-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-08 1:26 (63 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58-JsoAwUIsXounXO2b/Sh1tA@public.gmane.orgom>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci-x0m+Mc+nT7uljOmnV8AmnkElSqmLX1BE@public.gmane.org>
Date		: 2010-04-01 01:09 (39 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-25 20:04 (46 days old)
Message-ID	: <<201003252104.24965.maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-03-22 15:59 (49 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org
Date		: 2010-03-15 13:39 (56 days old)
Message-ID	: <4B9E38AF.70309-1SGGS//iJ+Y38rf8aCqVIw@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-14 7:58 (57 days old)
Message-ID	: <<20100314075831.GA13457-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (58 days old)
Message-ID	: <<alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15768
Subject		: Incorrectly calculated free blocks result in ENOSPC from writepage
Submitter	: Dmitry Monakhov <dmonakhov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Date		: 2010-04-12 11:24 (28 days old)
Handled-By	: Dmitry Monakhov <dmonakhov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Patch		: http://patchwork.ozlabs.org/patch/49989/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15729
Subject		: BUG: physmap modprobe & rmmod
Submitter	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Date		: 2010-04-02 20:40 (38 days old)
Message-ID	: <20100402134058.c4682716.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2
Handled-By	: Hartley Sweeten <hsweeten-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org>
Patch		: https://patchwork.kernel.org/patch/90497/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian-GANU6spQydw@public.gmane.org>
Date		: 2010-03-10 06:59 (61 days old)
Handled-By	: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11


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 from 2.6.33,
unresolved as well as resolved, at:

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

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

Thanks!

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (58 days old)
Message-ID	: <<alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (58 days old)
Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Sun, 9 May 2010 at 23:17, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> Date		: 2010-03-13 23:53 (58 days old)
> Message-ID	: <<alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

The bug is still present in -rc6, but Michael Ellerman has a patch[0] 
which made the warning go away.

@Michael: will you post your patch with a Sign-Off, so that it can be 
          pushed into mainline?

Thanks,
Christian.

[0] http://patchwork.ozlabs.org/patch/50557/

diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index ce94801..019581d 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -176,6 +176,24 @@ retry:
 	return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+	char *p, *fixed_name;
+
+	fixed_name = kstrdup(name, GFP_KERNEL);
+	if (!fixed_name) {
+		printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+				"name \"%s\"\n", name);
+	return name;
+	}
+
+	p = fixed_name;
+	while ((p = strstr(p, "/")))
+		*p++ = '_';
+
+	return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -212,6 +230,9 @@ void proc_device_tree_add_node(struct device_node *np,
 		if (duplicate_name(de, p))
 			p = fixup_name(np, de, p);
 
+		if (strstr(p, "/"))
+			p = unslash_name(p);
+
 		ent = __proc_device_tree_add_prop(de, pp, p);
 		if (ent == NULL)
 			break;
-- 
BOFH excuse #188:

..disk or the processor is on fire.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Sun, 9 May 2010 at 23:17, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (58 days old)
> Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

The bug is still present in -rc6, but Michael Ellerman has a patch[0] 
which made the warning go away.

@Michael: will you post your patch with a Sign-Off, so that it can be 
          pushed into mainline?

Thanks,
Christian.

[0] http://patchwork.ozlabs.org/patch/50557/

diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index ce94801..019581d 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -176,6 +176,24 @@ retry:
 	return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+	char *p, *fixed_name;
+
+	fixed_name = kstrdup(name, GFP_KERNEL);
+	if (!fixed_name) {
+		printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+				"name \"%s\"\n", name);
+	return name;
+	}
+
+	p = fixed_name;
+	while ((p = strstr(p, "/")))
+		*p++ = '_';
+
+	return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -212,6 +230,9 @@ void proc_device_tree_add_node(struct device_node *np,
 		if (duplicate_name(de, p))
 			p = fixup_name(np, de, p);
 
+		if (strstr(p, "/"))
+			p = unslash_name(p);
+
 		ent = __proc_device_tree_add_prop(de, pp, p);
 		if (ent == NULL)
 			break;
-- 
BOFH excuse #188:

..disk or the processor is on fire.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Christian Kujau]

On Sun, 9 May 2010 at 23:17, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (58 days old)
> Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

The bug is still present in -rc6, but Michael Ellerman has a patch[0] 
which made the warning go away.

@Michael: will you post your patch with a Sign-Off, so that it can be 
          pushed into mainline?

Thanks,
Christian.

[0] http://patchwork.ozlabs.org/patch/50557/

diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
index ce94801..019581d 100644
--- a/fs/proc/proc_devtree.c
+++ b/fs/proc/proc_devtree.c
@@ -176,6 +176,24 @@ retry:
 	return fixed_name;
 }
 
+static const char *unslash_name(const char *name)
+{
+	char *p, *fixed_name;
+
+	fixed_name = kstrdup(name, GFP_KERNEL);
+	if (!fixed_name) {
+		printk(KERN_ERR "device-tree: Out of memory trying to unslash "
+				"name \"%s\"\n", name);
+	return name;
+	}
+
+	p = fixed_name;
+	while ((p = strstr(p, "/")))
+		*p++ = '_';
+
+	return fixed_name;
+}
+
 /*
  * Process a node, adding entries for its children and its properties.
  */
@@ -212,6 +230,9 @@ void proc_device_tree_add_node(struct device_node *np,
 		if (duplicate_name(de, p))
 			p = fixup_name(np, de, p);
 
+		if (strstr(p, "/"))
+			p = unslash_name(p);
+
 		ent = __proc_device_tree_add_prop(de, pp, p);
 		if (ent == NULL)
 			break;
-- 
BOFH excuse #188:

..disk or the processor is on fire.

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Sun, 2010-05-09 at 15:27 -0700, Christian Kujau wrote:
> On Sun, 9 May 2010 at 23:17, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> > Date		: 2010-03-13 23:53 (58 days old)
> > Message-ID	: <<alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> The bug is still present in -rc6, but Michael Ellerman has a patch[0] 
> which made the warning go away.
> 
> @Michael: will you post your patch with a Sign-Off, so that it can be 
>           pushed into mainline?

No, Benh and I decided it's better to just drop those properties all
together. But it's too late in this cycle for a patch like that just to
fix a warning - so we'll do that patch for 35.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Sun, 2010-05-09 at 15:27 -0700, Christian Kujau wrote:
> On Sun, 9 May 2010 at 23:17, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists@nerdbynature.de>
> > Date		: 2010-03-13 23:53 (58 days old)
> > Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> The bug is still present in -rc6, but Michael Ellerman has a patch[0] 
> which made the warning go away.
> 
> @Michael: will you post your patch with a Sign-Off, so that it can be 
>           pushed into mainline?

No, Benh and I decided it's better to just drop those properties all
together. But it's too late in this cycle for a patch like that just to
fix a warning - so we'll do that patch for 35.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Michael Ellerman]

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

On Sun, 2010-05-09 at 15:27 -0700, Christian Kujau wrote:
> On Sun, 9 May 2010 at 23:17, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists@nerdbynature.de>
> > Date		: 2010-03-13 23:53 (58 days old)
> > Message-ID	: <<alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> The bug is still present in -rc6, but Michael Ellerman has a patch[0] 
> which made the warning go away.
> 
> @Michael: will you post your patch with a Sign-Off, so that it can be 
>           pushed into mainline?

No, Benh and I decided it's better to just drop those properties all
together. But it's too late in this cycle for a patch like that just to
fix a warning - so we'll do that patch for 35.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

2.6.34-rc6-git2: Reported regressions from 2.6.33

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.33,
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 regressions from 2.6.33, 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
  ----------------------------------------
  2010-05-04       76       26          22
  2010-04-20       64       35          34
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15880
Subject		: Very bad regression from 2.6.33 as of 1600f9def
Submitter	: Alex Elsayed <eternaleye@gmail.com>
Date		: 2010-04-29 2:28 (6 days old)
Message-ID	: <loom.20100429T041908-663@post.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=127250825306178&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15863
Subject		: 2.6.34-rc5-git7 (plus all patches) -- another suspicious rcu_dereference_check() usage.
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-04-27 0:51 (8 days old)
Message-ID	: <h2ya44ae5cd1004261751waa5cb65ei3d139cbcfa2cc5cf@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127232949104878&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15862
Subject		: 2.6.34-rc4/5: iwlagn unusable until reload
Submitter	: Nico Schottelius <nico-linux-20100427@schottelius.org>
Date		: 2010-04-27 7:49 (8 days old)
Message-ID	: <20100427074934.GB3261@ikn.schottelius.org>
References	: http://marc.info/?l=linux-kernel&m=127235784004839&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15858
Subject		: [2.6.34-rc5] bad page state copying to/from HFS+ filesystem...
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2010-04-25 21:14 (10 days old)
Message-ID	: <v2k6278d2221004251414kbbcc41baw78b86120d81dce7d@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127223008621881&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject		: reiserfs locking
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2010-04-15 21:02 (20 days old)
Message-ID	: <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127136535323933&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15790
Subject		: Meta-Bug: Regressions
Submitter	: Florian Mickler <fmickler@gmx.de>
Date		: 2010-04-15 18:21 (20 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15788
Subject		: external usb sound card doesn't work after resume
Submitter	: François Valenduc <francois.valenduc@tvcablenet.be>
Date		: 2010-04-15 10:16 (20 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 20:14 (52 days old)
Message-ID	: <20100314201434.GE22059@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi@intel.com>
Date		: 2010-03-25 8:40 (41 days old)
First-Bad-Commit: http://git.kernel.org/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel@alexs-hp.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl@linux-foundation.org>
		  Pekka Enberg <penberg@cs.helsinki.fi>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-04-01 6:06 (34 days old)
Message-ID	: <20100401060624.GA1329@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date		: 2010-03-31 10:21 (35 days old)
Message-ID	: <<20100331102142.GA3294@swordfish.minsk.epam.com>>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-03-28 11:31 (38 days old)
Message-ID	: <1269775909.5301.4.camel@localhost.localdomain>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2010-03-27 16:11 (39 days old)
Message-ID	: <20100327161104.GA12043@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-03-08 1:26 (58 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date		: 2010-04-01 01:09 (34 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2010-03-25 20:04 (41 days old)
Message-ID	: <<201003252104.24965.maciej.rutecki@gmail.com>>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15625
Subject		: BUG: 2.6.34-rc1, RIP is (null)
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-03-18 22:22 (48 days old)
Message-ID	: <4BA2A7A9.4080503@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=126895098217351&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15611
Subject		: Failure with the 2.6.34-rc1 kernel
Submitter	: Rupjyoti Sarmah <rsarmah@amcc.com>
Date		: 2010-03-16 15:45 (50 days old)
Message-ID	: <AC311A8E81420D4EBC1F26E6479848FE065B7D3D@SDCEXCHANGE01.ad.amcc.com>
References	: http://marc.info/?l=linux-kernel&m=126875435718396&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel@oracle.com>
Date		: 2010-03-22 15:59 (44 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev@fami-braun.de
Date		: 2010-03-15 13:39 (51 days old)
Message-ID	: <4B9E38AF.70309@fami-braun.de>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 7:58 (52 days old)
Message-ID	: <20100314075831.GA13457@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (53 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15893
Subject		: Alps: No edge-scrolling since 2.6.34-rc5
Submitter	: Felix Zweig <f.zweig@yahoo.de>
Date		: 2010-05-01 16:23 (4 days old)
Handled-By	:  Dan Carpenter <error27@gmail.com>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=26218


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15768
Subject		: Incorrectly calculated free blocks result in ENOSPC from writepage
Submitter	: Dmitry Monakhov <dmonakhov@openvz.org>
Date		: 2010-04-12 11:24 (23 days old)
Handled-By	: Dmitry Monakhov <dmonakhov@openvz.org>
Patch		: http://patchwork.ozlabs.org/patch/49989/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15729
Subject		: BUG: physmap modprobe & rmmod
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-04-02 20:40 (33 days old)
Message-ID	: <20100402134058.c4682716.randy.dunlap@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=127024096210230&w=2
Handled-By	: Hartley Sweeten <hsweeten@visionengravers.com>
Patch		: https://patchwork.kernel.org/patch/90497/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2010-03-10 06:59 (56 days old)
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11


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 from 2.6.33,
unresolved as well as resolved, at:

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

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-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (53 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Stefan Lippers-Hollmann]

Hi

On Wednesday 05 May 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> Date		: 2010-03-13 23:53 (53 days old)
> Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Still valid for b2c2_flexcop_pci in 2.6.34-rc6-git2:

[    8.736930] Linux video capture interface: v2.00
[    8.809720] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
[    8.818680] flexcop-pci: will use the HW PID filter.
[    8.818685] flexcop-pci: card revision 2
[    8.818694] b2c2_flexcop_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    8.818794] ------------[ cut here ]------------
[    8.818799] WARNING: at /tmp/buildd/linux-sidux-2.6-2.6.34~rc6-git2/debian/build/source_amd64_none/fs/proc/generic.c:317 __xlate_proc_name+0xb5/0xd0()
[    8.818801] Hardware name: EP45-DS3
[    8.818802] name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
[    8.818804] Modules linked in: b2c2_flexcop_pci(+) cx88xx b2c2_flexcop rfkill v4l2_common ir_common videodev drm snd_pcm snd_seq rtc_cmos snd_timer rtc_core snd_seq_device rtc_lib v4l1_compat tveeprom v4l2_compat_ioctl32 ir_core dvb_core snd videobuf_dma_sg cx24123 cx24113 videobuf_core s5h1420 tpm_tis led_class btcx_risc tpm i2c_i801 i2c_algo_bit tpm_bios i2c_core evdev intel_agp soundcore snd_page_alloc button processor ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom sd_mod usbhid hid uhci_hcd ahci firewire_ohci libata firewire_core crc_itu_t ehci_hcd r8169 mii scsi_mod thermal usbcore nls_base [last unloaded: scsi_wait_scan]
[    8.818832] Pid: 1064, comm: modprobe Not tainted 2.6.34-rc6-sidux-amd64 #1
[    8.818833] Call Trace:
[    8.818837]  [<ffffffff8104ba83>] ? warn_slowpath_common+0x73/0xb0
[    8.818839]  [<ffffffff8104bb20>] ? warn_slowpath_fmt+0x40/0x50
[    8.818842]  [<ffffffff8114f545>] ? __xlate_proc_name+0xb5/0xd0
[    8.818844]  [<ffffffff8114fb2e>] ? __proc_create+0x7e/0x150
[    8.818846]  [<ffffffff811504e7>] ? proc_mkdir_mode+0x27/0x60
[    8.818849]  [<ffffffff8109fb55>] ? register_handler_proc+0x115/0x130
[    8.818852]  [<ffffffff8109d4c1>] ? __setup_irq+0x1d1/0x330
[    8.818855]  [<ffffffffa03bc160>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
[    8.818858]  [<ffffffff8109d735>] ? request_threaded_irq+0x115/0x1b0
[    8.818860]  [<ffffffffa03bc495>] ? flexcop_pci_probe+0x1a5/0x330 [b2c2_flexcop_pci]
[    8.818864]  [<ffffffff811ceef2>] ? local_pci_probe+0x12/0x20
[    8.818867]  [<ffffffff811d02ca>] ? pci_device_probe+0x10a/0x130
[    8.818870]  [<ffffffff8125cdda>] ? driver_sysfs_add+0x5a/0x80
[    8.818872]  [<ffffffff8125cf03>] ? driver_probe_device+0x93/0x190
[    8.818874]  [<ffffffff8125d093>] ? __driver_attach+0x93/0xa0
[    8.818876]  [<ffffffff8125d000>] ? __driver_attach+0x0/0xa0
[    8.818878]  [<ffffffff8125c638>] ? bus_for_each_dev+0x58/0x80
[    8.818880]  [<ffffffff8125be70>] ? bus_add_driver+0xb0/0x250
[    8.818882]  [<ffffffff8125d38a>] ? driver_register+0x6a/0x130
[    8.818884]  [<ffffffff811d056c>] ? __pci_register_driver+0x4c/0xc0
[    8.818887]  [<ffffffffa03bf000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[    8.818890]  [<ffffffff81002044>] ? do_one_initcall+0x34/0x1a0
[    8.818893]  [<ffffffff8107d15f>] ? sys_init_module+0xdf/0x260
[    8.818896]  [<ffffffff81009f42>] ? system_call_fastpath+0x16/0x1b
[    8.818897] ---[ end trace 46b5c98323696f39 ]---
[    8.822389] DVB: registering new adapter (FlexCop Digital TV device)
[    8.823874] b2c2-flexcop: MAC address = 00:d0:d7:0c:83:d6

Regards
	Stefan Lippers-Hollmann

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Stefan Lippers-Hollmann]

Hi

On Wednesday 05 May 2010, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.33.  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=15589
> Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> Submitter	: Christian Kujau <lists@nerdbynature.de>
> Date		: 2010-03-13 23:53 (53 days old)
> Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

Still valid for b2c2_flexcop_pci in 2.6.34-rc6-git2:

[    8.736930] Linux video capture interface: v2.00
[    8.809720] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
[    8.818680] flexcop-pci: will use the HW PID filter.
[    8.818685] flexcop-pci: card revision 2
[    8.818694] b2c2_flexcop_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    8.818794] ------------[ cut here ]------------
[    8.818799] WARNING: at /tmp/buildd/linux-sidux-2.6-2.6.34~rc6-git2/debian/build/source_amd64_none/fs/proc/generic.c:317 __xlate_proc_name+0xb5/0xd0()
[    8.818801] Hardware name: EP45-DS3
[    8.818802] name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
[    8.818804] Modules linked in: b2c2_flexcop_pci(+) cx88xx b2c2_flexcop rfkill v4l2_common ir_common videodev drm snd_pcm snd_seq rtc_cmos snd_timer rtc_core snd_seq_device rtc_lib v4l1_compat tveeprom v4l2_compat_ioctl32 ir_core dvb_core snd videobuf_dma_sg cx24123 cx24113 videobuf_core s5h1420 tpm_tis led_class btcx_risc tpm i2c_i801 i2c_algo_bit tpm_bios i2c_core evdev intel_agp soundcore snd_page_alloc button processor ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom sd_mod usbhid hid uhci_hcd ahci firewire_ohci libata firewire_core crc_itu_t ehci_hcd r8169 mii scsi_mod thermal usbcore nls_base [last unloaded: scsi_wait_scan]
[    8.818832] Pid: 1064, comm: modprobe Not tainted 2.6.34-rc6-sidux-amd64 #1
[    8.818833] Call Trace:
[    8.818837]  [<ffffffff8104ba83>] ? warn_slowpath_common+0x73/0xb0
[    8.818839]  [<ffffffff8104bb20>] ? warn_slowpath_fmt+0x40/0x50
[    8.818842]  [<ffffffff8114f545>] ? __xlate_proc_name+0xb5/0xd0
[    8.818844]  [<ffffffff8114fb2e>] ? __proc_create+0x7e/0x150
[    8.818846]  [<ffffffff811504e7>] ? proc_mkdir_mode+0x27/0x60
[    8.818849]  [<ffffffff8109fb55>] ? register_handler_proc+0x115/0x130
[    8.818852]  [<ffffffff8109d4c1>] ? __setup_irq+0x1d1/0x330
[    8.818855]  [<ffffffffa03bc160>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
[    8.818858]  [<ffffffff8109d735>] ? request_threaded_irq+0x115/0x1b0
[    8.818860]  [<ffffffffa03bc495>] ? flexcop_pci_probe+0x1a5/0x330 [b2c2_flexcop_pci]
[    8.818864]  [<ffffffff811ceef2>] ? local_pci_probe+0x12/0x20
[    8.818867]  [<ffffffff811d02ca>] ? pci_device_probe+0x10a/0x130
[    8.818870]  [<ffffffff8125cdda>] ? driver_sysfs_add+0x5a/0x80
[    8.818872]  [<ffffffff8125cf03>] ? driver_probe_device+0x93/0x190
[    8.818874]  [<ffffffff8125d093>] ? __driver_attach+0x93/0xa0
[    8.818876]  [<ffffffff8125d000>] ? __driver_attach+0x0/0xa0
[    8.818878]  [<ffffffff8125c638>] ? bus_for_each_dev+0x58/0x80
[    8.818880]  [<ffffffff8125be70>] ? bus_add_driver+0xb0/0x250
[    8.818882]  [<ffffffff8125d38a>] ? driver_register+0x6a/0x130
[    8.818884]  [<ffffffff811d056c>] ? __pci_register_driver+0x4c/0xc0
[    8.818887]  [<ffffffffa03bf000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[    8.818890]  [<ffffffff81002044>] ? do_one_initcall+0x34/0x1a0
[    8.818893]  [<ffffffff8107d15f>] ? sys_init_module+0xdf/0x260
[    8.818896]  [<ffffffff81009f42>] ? system_call_fastpath+0x16/0x1b
[    8.818897] ---[ end trace 46b5c98323696f39 ]---
[    8.822389] DVB: registering new adapter (FlexCop Digital TV device)
[    8.823874] b2c2-flexcop: MAC address = 00:d0:d7:0c:83:d6

Regards
	Stefan Lippers-Hollmann

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Wednesday 05 May 2010, Stefan Lippers-Hollmann wrote:
> Hi
> 
> On Wednesday 05 May 2010, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
> > Date		: 2010-03-13 23:53 (53 days old)
> > Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> Still valid for b2c2_flexcop_pci in 2.6.34-rc6-git2:
> 
> [    8.736930] Linux video capture interface: v2.00
> [    8.809720] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
> [    8.818680] flexcop-pci: will use the HW PID filter.
> [    8.818685] flexcop-pci: card revision 2
> [    8.818694] b2c2_flexcop_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [    8.818794] ------------[ cut here ]------------
> [    8.818799] WARNING: at /tmp/buildd/linux-sidux-2.6-2.6.34~rc6-git2/debian/build/source_amd64_none/fs/proc/generic.c:317 __xlate_proc_name+0xb5/0xd0()
> [    8.818801] Hardware name: EP45-DS3
> [    8.818802] name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
> [    8.818804] Modules linked in: b2c2_flexcop_pci(+) cx88xx b2c2_flexcop rfkill v4l2_common ir_common videodev drm snd_pcm snd_seq rtc_cmos snd_timer rtc_core snd_seq_device rtc_lib v4l1_compat tveeprom v4l2_compat_ioctl32 ir_core dvb_core snd videobuf_dma_sg cx24123 cx24113 videobuf_core s5h1420 tpm_tis led_class btcx_risc tpm i2c_i801 i2c_algo_bit tpm_bios i2c_core evdev intel_agp soundcore snd_page_alloc button processor ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom sd_mod usbhid hid uhci_hcd ahci firewire_ohci libata firewire_core crc_itu_t ehci_hcd r8169 mii scsi_mod thermal usbcore nls_base [last unloaded: scsi_wait_scan]
> [    8.818832] Pid: 1064, comm: modprobe Not tainted 2.6.34-rc6-sidux-amd64 #1
> [    8.818833] Call Trace:
> [    8.818837]  [<ffffffff8104ba83>] ? warn_slowpath_common+0x73/0xb0
> [    8.818839]  [<ffffffff8104bb20>] ? warn_slowpath_fmt+0x40/0x50
> [    8.818842]  [<ffffffff8114f545>] ? __xlate_proc_name+0xb5/0xd0
> [    8.818844]  [<ffffffff8114fb2e>] ? __proc_create+0x7e/0x150
> [    8.818846]  [<ffffffff811504e7>] ? proc_mkdir_mode+0x27/0x60
> [    8.818849]  [<ffffffff8109fb55>] ? register_handler_proc+0x115/0x130
> [    8.818852]  [<ffffffff8109d4c1>] ? __setup_irq+0x1d1/0x330
> [    8.818855]  [<ffffffffa03bc160>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
> [    8.818858]  [<ffffffff8109d735>] ? request_threaded_irq+0x115/0x1b0
> [    8.818860]  [<ffffffffa03bc495>] ? flexcop_pci_probe+0x1a5/0x330 [b2c2_flexcop_pci]
> [    8.818864]  [<ffffffff811ceef2>] ? local_pci_probe+0x12/0x20
> [    8.818867]  [<ffffffff811d02ca>] ? pci_device_probe+0x10a/0x130
> [    8.818870]  [<ffffffff8125cdda>] ? driver_sysfs_add+0x5a/0x80
> [    8.818872]  [<ffffffff8125cf03>] ? driver_probe_device+0x93/0x190
> [    8.818874]  [<ffffffff8125d093>] ? __driver_attach+0x93/0xa0
> [    8.818876]  [<ffffffff8125d000>] ? __driver_attach+0x0/0xa0
> [    8.818878]  [<ffffffff8125c638>] ? bus_for_each_dev+0x58/0x80
> [    8.818880]  [<ffffffff8125be70>] ? bus_add_driver+0xb0/0x250
> [    8.818882]  [<ffffffff8125d38a>] ? driver_register+0x6a/0x130
> [    8.818884]  [<ffffffff811d056c>] ? __pci_register_driver+0x4c/0xc0
> [    8.818887]  [<ffffffffa03bf000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
> [    8.818890]  [<ffffffff81002044>] ? do_one_initcall+0x34/0x1a0
> [    8.818893]  [<ffffffff8107d15f>] ? sys_init_module+0xdf/0x260
> [    8.818896]  [<ffffffff81009f42>] ? system_call_fastpath+0x16/0x1b
> [    8.818897] ---[ end trace 46b5c98323696f39 ]---
> [    8.822389] DVB: registering new adapter (FlexCop Digital TV device)
> [    8.823874] b2c2-flexcop: MAC address = 00:d0:d7:0c:83:d6

Thanks for the update.

Rafael

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

On Wednesday 05 May 2010, Stefan Lippers-Hollmann wrote:
> Hi
> 
> On Wednesday 05 May 2010, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.33.  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=15589
> > Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
> > Submitter	: Christian Kujau <lists@nerdbynature.de>
> > Date		: 2010-03-13 23:53 (53 days old)
> > Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
> > References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2
> 
> Still valid for b2c2_flexcop_pci in 2.6.34-rc6-git2:
> 
> [    8.736930] Linux video capture interface: v2.00
> [    8.809720] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
> [    8.818680] flexcop-pci: will use the HW PID filter.
> [    8.818685] flexcop-pci: card revision 2
> [    8.818694] b2c2_flexcop_pci 0000:06:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [    8.818794] ------------[ cut here ]------------
> [    8.818799] WARNING: at /tmp/buildd/linux-sidux-2.6-2.6.34~rc6-git2/debian/build/source_amd64_none/fs/proc/generic.c:317 __xlate_proc_name+0xb5/0xd0()
> [    8.818801] Hardware name: EP45-DS3
> [    8.818802] name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
> [    8.818804] Modules linked in: b2c2_flexcop_pci(+) cx88xx b2c2_flexcop rfkill v4l2_common ir_common videodev drm snd_pcm snd_seq rtc_cmos snd_timer rtc_core snd_seq_device rtc_lib v4l1_compat tveeprom v4l2_compat_ioctl32 ir_core dvb_core snd videobuf_dma_sg cx24123 cx24113 videobuf_core s5h1420 tpm_tis led_class btcx_risc tpm i2c_i801 i2c_algo_bit tpm_bios i2c_core evdev intel_agp soundcore snd_page_alloc button processor ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom sd_mod usbhid hid uhci_hcd ahci firewire_ohci libata firewire_core crc_itu_t ehci_hcd r8169 mii scsi_mod thermal usbcore nls_base [last unloaded: scsi_wait_scan]
> [    8.818832] Pid: 1064, comm: modprobe Not tainted 2.6.34-rc6-sidux-amd64 #1
> [    8.818833] Call Trace:
> [    8.818837]  [<ffffffff8104ba83>] ? warn_slowpath_common+0x73/0xb0
> [    8.818839]  [<ffffffff8104bb20>] ? warn_slowpath_fmt+0x40/0x50
> [    8.818842]  [<ffffffff8114f545>] ? __xlate_proc_name+0xb5/0xd0
> [    8.818844]  [<ffffffff8114fb2e>] ? __proc_create+0x7e/0x150
> [    8.818846]  [<ffffffff811504e7>] ? proc_mkdir_mode+0x27/0x60
> [    8.818849]  [<ffffffff8109fb55>] ? register_handler_proc+0x115/0x130
> [    8.818852]  [<ffffffff8109d4c1>] ? __setup_irq+0x1d1/0x330
> [    8.818855]  [<ffffffffa03bc160>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
> [    8.818858]  [<ffffffff8109d735>] ? request_threaded_irq+0x115/0x1b0
> [    8.818860]  [<ffffffffa03bc495>] ? flexcop_pci_probe+0x1a5/0x330 [b2c2_flexcop_pci]
> [    8.818864]  [<ffffffff811ceef2>] ? local_pci_probe+0x12/0x20
> [    8.818867]  [<ffffffff811d02ca>] ? pci_device_probe+0x10a/0x130
> [    8.818870]  [<ffffffff8125cdda>] ? driver_sysfs_add+0x5a/0x80
> [    8.818872]  [<ffffffff8125cf03>] ? driver_probe_device+0x93/0x190
> [    8.818874]  [<ffffffff8125d093>] ? __driver_attach+0x93/0xa0
> [    8.818876]  [<ffffffff8125d000>] ? __driver_attach+0x0/0xa0
> [    8.818878]  [<ffffffff8125c638>] ? bus_for_each_dev+0x58/0x80
> [    8.818880]  [<ffffffff8125be70>] ? bus_add_driver+0xb0/0x250
> [    8.818882]  [<ffffffff8125d38a>] ? driver_register+0x6a/0x130
> [    8.818884]  [<ffffffff811d056c>] ? __pci_register_driver+0x4c/0xc0
> [    8.818887]  [<ffffffffa03bf000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
> [    8.818890]  [<ffffffff81002044>] ? do_one_initcall+0x34/0x1a0
> [    8.818893]  [<ffffffff8107d15f>] ? sys_init_module+0xdf/0x260
> [    8.818896]  [<ffffffff81009f42>] ? system_call_fastpath+0x16/0x1b
> [    8.818897] ---[ end trace 46b5c98323696f39 ]---
> [    8.822389] DVB: registering new adapter (FlexCop Digital TV device)
> [    8.823874] b2c2-flexcop: MAC address = 00:d0:d7:0c:83:d6

Thanks for the update.

Rafael

2.6.34-rc3-git6: Reported regressions from 2.6.33

[Rafael J. Wysocki]

[NOTE:
 The summary report of post-2.6.32 regressions will be sent later
 (hopefully tomorrow).]

This message contains a list of some regressions from 2.6.33,
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 regressions from 2.6.33, 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
  ----------------------------------------
  2010-04-07       48       35          33
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15719
Subject		: virtio_net causing kernel BUG when running under VirtualBox
Submitter	: Thomas Müller <thomas@mathtm.de>
Date		: 2010-03-27 14:32 (12 days old)
First-Bad-Commit: http://git.kernel.org/git/linus/9ab86bbcf8be755256f0a5e994e0b38af6b4d399
Message-ID	: <4BAE1707.2050803@mathtm.de>
References	: http://marc.info/?l=linux-kernel&m=126970039227740&w=4
Handled-By	: Shirley Ma <mashirle@us.ibm.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15718
Subject		: File corruption regression on NFS related to commit 1f36f774
Submitter	: Boaz Harrosh <bharrosh@panasas.com>
Date		: 2010-03-24 15:49 (15 days old)
First-Bad-Commit: http://git.kernel.org/git/linus/1f36f774b22a0ceb7dd33eca626746c81a97b6a5
Message-ID	: <4BAA3493.1030802@panasas.com>
References	: http://marc.info/?l=linux-kernel&m=126944579810350&w=4
Handled-By	: Al Viro <viro@zeniv.linux.org.uk>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15717
Subject		: bluetooth oops
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 20:14 (25 days old)
Message-ID	: <20100314201434.GE22059@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126859771528426&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15716
Subject		: ata2: lost interrupt with kernel 2.6.34-rc1
Submitter	: Andrew Benton <b3nton@gmail.com>
Date		: 2010-03-11 16:57 (28 days old)
Message-ID	: <4B992110.2090300@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126832670609705&w=4
Handled-By	: Jeff Garzik <jeff@garzik.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15715
Subject		: vmscan: underflow for get_scan_ratio
Submitter	: Shaohua Li <shaohua.li@intel.com>
Date		: 2010-03-30 5:53 (9 days old)
First-Bad-Commit: http://git.kernel.org/git/linus/84b18490d1f1bc7ed5095c929f78bc002eb70f26
Message-ID	: <20100330055304.GA2983@sli10-desk.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=126992842105754&w=4
Handled-By	: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
		  Wu Fengguang <fengguang.wu@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15713
Subject		: hackbench regression due to commit 9dfc6e68bfe6e
Submitter	: Alex Shi <alex.shi@intel.com>
Date		: 2010-03-25 8:40 (14 days old)
First-Bad-Commit: http://git.kernel.org/git/linus/9dfc6e68bfe6ee452efb1a4e9ca26a9007f2b864
Message-ID	: <1269506457.4513.141.camel@alexs-hp.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=126950632920682&w=4
Handled-By	: Christoph Lameter <cl@linux-foundation.org>
		  Pekka Enberg <penberg@cs.helsinki.fi>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15712
Subject		: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-04-01 6:06 (7 days old)
Message-ID	: <20100401060624.GA1329@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=127010200817402&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15711
Subject		: 2.6.34-rc3, BUG at mm/slab.c:2989
Submitter	: Heinz Diehl <htd@fancy-poultry.org>
Date		: 2010-04-01 17:52 (7 days old)
Message-ID	: <20100401175225.GA6581@fancy-poultry.org>
References	: http://marc.info/?l=linux-kernel&m=127014437406250&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject		: [r8169] WARNING: at net/sched/sch_generic.c
Submitter	: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date		: 2010-03-31 10:21 (8 days old)
Message-ID	: <20100331102142.GA3294@swordfish.minsk.epam.com>
References	: http://marc.info/?l=linux-kernel&m=127003090406108&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15674
Subject		: [2.6.34-rc2 NFS4 oops] open error path failure...
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2010-03-29 18:36 (10 days old)
Message-ID	: <6278d2221003291136p6481fe8emfb039403343c082@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126988782722711&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject		: 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-03-28 11:31 (11 days old)
Message-ID	: <1269775909.5301.4.camel@localhost.localdomain>
References	: http://marc.info/?l=linux-kernel&m=126977593326800&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15672
Subject		: KVM bug, git bisected
Submitter	: Kent Overstreet <kent.overstreet@gmail.com>
Date		: 2010-03-27 12:43 (12 days old)
First-Bad-Commit: http://git.kernel.org/git/linus/5beb49305251e5669852ed541e8e2f2f7696c53e
Message-ID	: <4BADFD74.8060904@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126969385121711&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15671
Subject		: intel graphic card hanging (Hangcheck timer elapsed... GPU hung)
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2010-03-27 16:11 (12 days old)
Message-ID	: <20100327161104.GA12043@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=126970883105262&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15669
Subject		: INFO: suspicious rcu_dereference_check()
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-03-08 1:26 (31 days old)
Message-ID	: <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126801163107713&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15668
Subject		: start_kernel(): bug: interrupts were enabled early
Submitter	: Rabin Vincent <rabin@rab.in>
Date		: 2010-03-25 19:53 (14 days old)
First-Bad-Commit: http://git.kernel.org/git/linus/773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9
Message-ID	: <20100325194100.GA2364@debian>
References	: http://marc.info/?l=linux-kernel&m=126954607216519&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject		: Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter	: Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date		: 2010-04-01 01:09 (7 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15661
Subject		: PROBLEM: crash on halt with 2.6.34-0.16.rc2.git0.fc14.x86_64
Submitter	: Jon Masters <jonathan@jonmasters.org>
Date		: 2010-03-26 15:29 (13 days old)
Message-ID	: <1269617372.3779.234.camel@localhost>
References	: http://marc.info/?l=linux-kernel&m=126961739803949&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15659
Subject		: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2010-03-25 20:04 (14 days old)
Message-ID	: <201003252104.24965.maciej.rutecki@gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126954749618319&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15655
Subject		: corrupt ext3 fs and partial freeze
Submitter	: Alban Browaeys <prahal@yahoo.com>
Date		: 2010-03-30 08:25 (9 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15625
Subject		: BUG: 2.6.34-rc1, RIP is (null)
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2010-03-18 22:22 (21 days old)
Message-ID	: <4BA2A7A9.4080503@oracle.com>
References	: http://marc.info/?l=linux-kernel&m=126895098217351&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15624
Subject		: [BUG] percpu misaligned allocation
Submitter	: Frederic Weisbecker <fweisbec@gmail.com>
Date		: 2010-03-18 4:49 (21 days old)
Message-ID	: <20100318044930.GC5045@nowhere>
References	: http://marc.info/?l=linux-kernel&m=126888780031992&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15619
Subject		: Regression - Linux 2.6.34-rc1 - i915 - Render error detected
Submitter	: Fabio Comolli <fabio.comolli@gmail.com>
Date		: 2010-03-17 21:58 (22 days old)
Message-ID	: <b637ec0b1003171458t524d168fiab52ce2b3431e3c9@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=126886311908558&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15615
Subject		: NULL pointer deref in task_is_waking
Submitter	: Amit Shah <shahamit@gmail.com>
Date		: 2010-03-23 04:04 (16 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15611
Subject		: Failure with the 2.6.34-rc1 kernel
Submitter	: Rupjyoti Sarmah <rsarmah@amcc.com>
Date		: 2010-03-16 15:45 (23 days old)
Message-ID	: <AC311A8E81420D4EBC1F26E6479848FE065B7D3D@SDCEXCHANGE01.ad.amcc.com>
References	: http://marc.info/?l=linux-kernel&m=126875435718396&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15610
Subject		: fsck leads to swapper - BUG: unable to handle kernel NULL pointer dereference & panic
Submitter	: Ozgur Yuksel <ozgur.yuksel@oracle.com>
Date		: 2010-03-22 15:59 (17 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15603
Subject		: lockdep warning at boot time when determining whether to resume
Submitter	: Sami Liedes <sliedes@cc.hut.fi>
Date		: 2010-03-22 00:03 (17 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15601
Subject		: [BUG] SLOB breaks Crypto
Submitter	: michael-dev@fami-braun.de
Date		: 2010-03-15 13:39 (24 days old)
Message-ID	: <4B9E38AF.70309@fami-braun.de>
References	: http://marc.info/?l=linux-kernel&m=126866044724539&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15600
Subject		: CONFIG_NO_BOOTMEM woes, 2.6.34-rc1
Submitter	: Avi Kivity <avi@redhat.com>
Date		: 2010-03-15 15:28 (24 days old)
Message-ID	: <4B9E5211.9000204@redhat.com>
References	: http://marc.info/?l=linux-kernel&m=126866691701926&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-03-14 7:58 (25 days old)
Message-ID	: <20100314075831.GA13457@elf.ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (26 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15553
Subject		: Screen backlight doesn't come back on after lid was closed (GM45)
Submitter	:  <bugs@kaijauch.de>
Date		: 2010-03-17 14:35 (22 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15551
Subject		: WARNING: at net/mac80211/work.c:811 ieee80211_work_work+0x7f/0xde8 [mac80211]()
Submitter	: Alex Zhavnerchik <alex.vizor@gmail.com>
Date		: 2010-03-16 22:03 (23 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15518
Subject		: CONFIG_NO_BOOTMEM=y breaks boot on 32bit
Submitter	: Daniel Vetter <daniel@ffwll.ch>
Date		: 2010-03-11 15:37 (28 days old)


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2010-03-10 06:59 (29 days old)
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15480
Subject		: [regression] Fails to boot properly unless given pci=nocrs
Submitter	: Yanko Kaneti <yaneti@declera.com>
Date		: 2010-03-09 01:24 (30 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch		: http://lkml.org/lkml/2010/3/11/512


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 from 2.6.33,
unresolved as well as resolved, at:

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

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-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (26 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2

2.6.34-rc2: Reported regressions from 2.6.33

[Rafael J. Wysocki]

[NOTES:
 * In this cycle the regressions reported by e-mail will only be put into the
   Bugzilla 1 week after they have been submitted, if not fixed in the
   meantime.  The reason is that some regressions are fixed in less than a
   week time and there's no point listing them.  [We also hope that people will 
   try to fix bugs faster to avoid being listed. ;-)]  If that works, we'll
   adopt it as a general rule.

 * All of the regressions reported by e-mail that are listed below have been
   put into the Bugzilla by Maciej, because I literally didn't have the time
   to do that (that's also why the summary reports are delayed).
   Thanks Maciej!]

This message contains a list of some regressions from 2.6.33,
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 regressions from 2.6.33, 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
  ----------------------------------------
  2010-03-21       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15590
Subject		: 2.6.34-rc1: regression: ^Z no longer stops sound
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-14 7:58 (8 days old)
Message-ID	: <20100314075831.GA13457-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126855353122623&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
Date		: 2010-03-13 23:53 (9 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493-uKsf7x9sgtqQ/Pez2Lbyp4QuADTiUCJX@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15584
Subject		: 2.6.34-rc1: lockdep warning on geode subnotebook
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-03-13 10:51 (9 days old)
Message-ID	: <20100313105109.GA9966-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126847750927601&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15555
Subject		: 2.6.34-rc1: kernel BUG at mm/slab.c:2989!
Submitter	: Américo Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-10 8:29 (12 days old)
Message-ID	: <2375c9f91003100029q7d64bbf7xce15eee97f7e2190-JsoAwUIsXounXO2b/Sh1tA@public.gmane.orgom>
References	: http://marc.info/?l=linux-kernel&m=126820979017089&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15549
Subject		: [2.6.34-rc1][libata] regression?
Submitter	: Etienne Basset <etienne.basset-Bf/eaXMDFuuXqB7oj33eUg@public.gmane.org>
Date		: 2010-03-09 21:47 (13 days old)
Message-ID	: <4B96C202.6050606-Bf/eaXMDFuuXqB7oj33eUg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126817180811846&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15548
Subject		: BUG: key f70f4b50 not in .data
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-09 10:27 (13 days old)
Message-ID	: <20100309102754.GA3316-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=126813046113130&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15533
Subject		: i915 fails to set mode in 2.6.34-rc1, ok in 2.6.33-rc8
Submitter	: Pete Zaitcev <zaitcev-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-13 20:37 (9 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15518
Subject		: CONFIG_NO_BOOTMEM=y breaks boot on 32bit
Submitter	: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Date		: 2010-03-11 15:37 (11 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15496
Subject		: 2.6.34-rc1 crashes early while startup
Submitter	: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Date		: 2010-03-09 19:40 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15495
Subject		: Flood of SELinux denials on polkitd
Submitter	: Alex Villacis Lasso <avillaci-x0m+Mc+nT7uljOmnV8AmnkElSqmLX1BE@public.gmane.org>
Date		: 2010-03-09 16:47 (13 days old)


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15537
Subject		: 2.6.34-rc1 hangs for 30 seconds when trying to access the disk
Submitter	: Andrew Benton <b3nton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-03-14 23:26 (8 days old)
Handled-By	: Jeff Garzik <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=25516


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15505
Subject		: No more b43 wireless interface since 2.6.34-rc1
Submitter	: Christian Casteyde <casteyde.christian-GANU6spQydw@public.gmane.org>
Date		: 2010-03-10 06:59 (12 days old)
Handled-By	: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Patch		: https://bugzilla.kernel.org/show_bug.cgi?id=15505#c11


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15480
Subject		: [regression] Fails to boot properly unless given pci=nocrs
Submitter	: Yanko Kaneti <yaneti-jUE9FD3ILm5BDgjK7y7TUQ@public.gmane.org>
Date		: 2010-03-09 01:24 (13 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Patch		: http://lkml.org/lkml/2010/3/11/512


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 from 2.6.33,
unresolved as well as resolved, at:

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

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

Thanks!

[Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

[Rafael J. Wysocki]

This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.33.  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=15589
Subject		: 2.6.34-rc1: Badness at fs/proc/generic.c:316
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2010-03-13 23:53 (9 days old)
Message-ID	: <alpine.DEB.2.01.1003131544340.5493@bogon.housecafe.de>
References	: http://marc.info/?l=linux-kernel&m=126852442903680&w=2