2.6.30-rc6: Reported regressions from 2.6.29

2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.29, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.29, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-05-16       81       36          33
  2009-04-25       55       36          26
  2009-04-17       37       35          28



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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
Subject		: cifs_close: NULL pointer dereference
Submitter	: Luca Tettamanti <kronos.it@gmail.com>
Date		: 2009-05-16 16:28 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13328
Subject		: b44: eth0: BUG! Timeout waiting for bit 00000002 of register 42c to clear.
Submitter	: Francis Moreau <francis.moro@gmail.com>
Date		: 2009-05-03 16:22 (14 days old)
References	: http://marc.info/?l=linux-kernel&m=124136778012280&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13327
Subject		: Regression: 2.6.30-rc5 and rt2x00 / rt2500pci
Submitter	: Ken Lewis <kennylewis@gmail.com>
Date		: 2009-05-15 14:40 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=124239988223614&w=4
Handled-By	: John W. Linville <linville@tuxdriver.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13326
Subject		: Null pointer dereference in rtc-cmos driver
Submitter	: Ozan Çağlayan <ozan@pardus.org.tr>
Date		: 2009-05-14 16:16 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231783704696&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
Subject		: 2.6.30-rc kills my box hard - and lockdep chains
Submitter	: Jonathan Corbet <corbet@lwn.net>
Date		: 2009-05-14 15:49 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13324
Subject		: panic when loading oprofile
Submitter	: Brandeburg, Jesse <jesse.brandeburg@intel.com>
Date		: 2009-05-13 22:30 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124225384311631&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13323
Subject		: 2.6.30-rc deadline scheduler performance regression for iozone over NFS
Submitter	: Jeff Moyer <jmoyer@redhat.com>
Date		: 2009-04-23 14:01 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124049547915450&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
Subject		: kernel crash with NULL pointer when boot
Submitter	: Martin Bammer <mrb74@gmx.at>
Date		: 2009-05-16 12:37 (1 days old)
References	: http://lkml.org/lkml/2009/5/16/100


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
Subject		: Page allocation failures with b43 and p54usb
Submitter	: Larry Finger <Larry.Finger@lwfinger.net>
Date		: 2009-04-29 21:01 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
Handled-By	: Johannes Berg <johannes@sipsolutions.net>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13318
Subject		: AGP doesn't work anymore on nforce2
Submitter	: Karsten Mehrhoff <kawime@gmx.de>
Date		: 2009-04-30 8:51 (17 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=59de2bebabc5027f93df999d59cc65df591c3e6e
References	: http://marc.info/?l=linux-kernel&m=124108156417560&w=4
Handled-By	: Shaohua Li <shaohua.li@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13306
Subject		: hibernate slow on _second_ run
Submitter	: Johannes Berg <johannes@sipsolutions.net>
Date		: 2009-05-14 09:34 (3 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
Submitter	: Ferenc Wagner <wferi@niif.hu>
Date		: 2009-05-12 21:28 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
Subject		: kernel panic -  not syncing : fatel exception in interupt
Submitter	: rob <rob1@housetosell.net>
Date		: 2009-05-12 19:34 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2009-05-12 7:59 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13294
Subject		: i915: drm: xorg leaks drm objects massively
Submitter	: Sergei Trofimovich <slyich@gmail.com>
Date		: 2009-05-10 19:56 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124198547027903&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13293
Subject		: Kernel BUG under network load with gianfar
Submitter	: Michael Guntsche <mike@it-loops.com>
Date		: 2009-05-03 13:36 (14 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0fd56bb5be6455d0d42241e65aed057244665e5e
References	: http://marc.info/?l=linux-kernel&m=124135824600924&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13285
Subject		: INTELFB: Colors display incorrectly
Submitter	: Dean Menezes <samanddeanus@yahoo.com>
Date		: 2009-05-12 01:40 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13250
Subject		: Side channel of Intel HDA chip doesn't work anymore, did work with 2.6.29
Submitter	: Andreas Juch <kernel-bt@juch.cc>
Date		: 2009-05-05 10:14 (12 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
Subject		: possible circular locking dependency detected
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2009-05-04 16:56 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
Subject		: horizontal strips of the screen frozen
Submitter	: Justin Madru <jdm64@gawab.com>
Date		: 2009-04-24 20:59 (23 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13180
Subject		: 2.6.30-rc2: WARNING at i915_gem.c for i915_gem_idle
Submitter	: Niel Lambrechts <niel.lambrechts@gmail.com>
Date		: 2009-04-21 21:35 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124034980819102&w=4
		  http://lkml.org/lkml/2009/4/27/290


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13179
Subject		: CD-R: wodim intermittent failures
Submitter	: Andy Isaacson <adi@hexapodia.org>
Date		: 2009-04-21 1:52 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124027879214231&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
Subject		: 2.6.30-rc2-git7 build problem
Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
Date		: 2009-04-21 13:39 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
		  http://lkml.org/lkml/2009/4/27/56


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13171
Subject		: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
Submitter	: Alex Bennee <kernel-hacker@bennee.com>
Date		: 2009-04-19 6:27 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=124022460014812&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13156
Subject		: keyboard backlight brightness up/down keys doesn't work
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2009-04-23 20:46 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13148
Subject		: resume after suspend-to-ram broken on Sony Vaio VGN-SR19VN when sony-laptop driver present
Submitter	: fanderay <fanderay4@googlemail.com>
Date		: 2009-04-22 14:39 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2009-04-15 12:43 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13119
Subject		: Trouble with make-install from a NFS mount
Submitter	: Gregory Haskins <ghaskins@novell.com>
Date		: 2009-04-14 21:32 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=123974482327044&w=4
Handled-By	: H. Peter Anvin <hpa@zytor.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
Date		: 2009-04-10 16:05 (37 days old)
References	: http://lkml.org/lkml/2009/4/10/111
		  http://lkml.org/lkml/2009/4/25/83
Handled-By	: Eric Dumazet <dada1@cosmosbay.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
Subject		: Can't boot with nosmp
Submitter	: Stephen Hemminger <shemminger@vyatta.com>
Date		: 2009-04-15 4:18 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
Handled-By	: Dan Williams <dan.j.williams@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
Submitter	: Kumar Gala <galak@kernel.crashing.org>
Date		: 2009-04-09 15:43 (38 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
		  http://lkml.org/lkml/2009/4/10/193
Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13069
Subject		: regression in 2.6.29-git3 on SH/Dreamcast
Submitter	: Adrian McMenamin <adrian@newgolddream.dyndns.info>
Date		: 2009-03-29 19:04 (49 days old)
References	: http://marc.info/?l=linux-kernel&m=123835353115372&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
Subject		: Lockdep warining in inotify_dev_queue_event
Submitter	: Sachin Sant <sachinp@in.ibm.com>
Date		: 2009-04-05 12:37 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13125
Subject		: active uvcvideo breaks over suspend
Submitter	: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Date		: 2009-04-15 10:12 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979009508840&w=4
Handled-By	: Ming Lei <tom.leiming@gmail.com>
Patch		: http://lkml.org/lkml/2009/4/18/5


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2009-04-16 19:23 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
Handled-By	: Jeff Mahoney <jeffm@suse.com>
Patch		: http://lkml.org/lkml/2009/5/10/91


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13109
Subject		: High latency on /sys/class/thermal
Submitter	: Tiago Simões Batista <tiagosbatista@gmail.com>
Date		: 2009-04-11 14:56 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123946182301248&w=4
Handled-By	: Zhang Rui <rui.zhang@intel.com>
		  Alexey Starikovskiy <astarikovskiy@suse.de>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21061
		  http://bugzilla.kernel.org/attachment.cgi?id=21282


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

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

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

Thanks,
Rafael

2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.29, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.29, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-05-16       81       36          33
  2009-04-25       55       36          26
  2009-04-17       37       35          28



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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
Subject		: cifs_close: NULL pointer dereference
Submitter	: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-16 16:28 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13328
Subject		: b44: eth0: BUG! Timeout waiting for bit 00000002 of register 42c to clear.
Submitter	: Francis Moreau <francis.moro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-03 16:22 (14 days old)
References	: http://marc.info/?l=linux-kernel&m=124136778012280&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13327
Subject		: Regression: 2.6.30-rc5 and rt2x00 / rt2500pci
Submitter	: Ken Lewis <kennylewis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-15 14:40 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=124239988223614&w=4
Handled-By	: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13326
Subject		: Null pointer dereference in rtc-cmos driver
Submitter	: Ozan Çağlayan <ozan-caicS1wCkhO6A22drWdTBw@public.gmane.org>
Date		: 2009-05-14 16:16 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231783704696&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
Subject		: 2.6.30-rc kills my box hard - and lockdep chains
Submitter	: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>
Date		: 2009-05-14 15:49 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13324
Subject		: panic when loading oprofile
Submitter	: Brandeburg, Jesse <jesse.brandeburg-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-13 22:30 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124225384311631&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13323
Subject		: 2.6.30-rc deadline scheduler performance regression for iozone over NFS
Submitter	: Jeff Moyer <jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-23 14:01 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124049547915450&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
Subject		: kernel crash with NULL pointer when boot
Submitter	: Martin Bammer <mrb74-RbZlAiThDcE@public.gmane.org>
Date		: 2009-05-16 12:37 (1 days old)
References	: http://lkml.org/lkml/2009/5/16/100


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
Subject		: Page allocation failures with b43 and p54usb
Submitter	: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Date		: 2009-04-29 21:01 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
Handled-By	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13318
Subject		: AGP doesn't work anymore on nforce2
Submitter	: Karsten Mehrhoff <kawime-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-04-30 8:51 (17 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=59de2bebabc5027f93df999d59cc65df591c3e6e
References	: http://marc.info/?l=linux-kernel&m=124108156417560&w=4
Handled-By	: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13306
Subject		: hibernate slow on _second_ run
Submitter	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Date		: 2009-05-14 09:34 (3 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
Submitter	: Ferenc Wagner <wferi-eEbw3PyuezQ@public.gmane.org>
Date		: 2009-05-12 21:28 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
Subject		: kernel panic -  not syncing : fatel exception in interupt
Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
Date		: 2009-05-12 19:34 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
Submitter	: Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-12 7:59 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13294
Subject		: i915: drm: xorg leaks drm objects massively
Submitter	: Sergei Trofimovich <slyich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-10 19:56 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124198547027903&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13293
Subject		: Kernel BUG under network load with gianfar
Submitter	: Michael Guntsche <mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
Date		: 2009-05-03 13:36 (14 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0fd56bb5be6455d0d42241e65aed057244665e5e
References	: http://marc.info/?l=linux-kernel&m=124135824600924&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13285
Subject		: INTELFB: Colors display incorrectly
Submitter	: Dean Menezes <samanddeanus-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-12 01:40 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13250
Subject		: Side channel of Intel HDA chip doesn't work anymore, did work with 2.6.29
Submitter	: Andreas Juch <kernel-bt-Sk8biX5uX1I@public.gmane.org>
Date		: 2009-05-05 10:14 (12 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
Subject		: possible circular locking dependency detected
Submitter	: Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-04 16:56 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
Subject		: horizontal strips of the screen frozen
Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-24 20:59 (23 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13180
Subject		: 2.6.30-rc2: WARNING at i915_gem.c for i915_gem_idle
Submitter	: Niel Lambrechts <niel.lambrechts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-21 21:35 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124034980819102&w=4
		  http://lkml.org/lkml/2009/4/27/290


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13179
Subject		: CD-R: wodim intermittent failures
Submitter	: Andy Isaacson <adi-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
Date		: 2009-04-21 1:52 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124027879214231&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
Subject		: 2.6.30-rc2-git7 build problem
Submitter	: Martin Knoblauch <spamtrap-Ys4E+72pFW0hFhg+JK9F0w@public.gmane.org>
Date		: 2009-04-21 13:39 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
		  http://lkml.org/lkml/2009/4/27/56


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13171
Subject		: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
Submitter	: Alex Bennee <kernel-hacker-jriKODhXDevQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-19 6:27 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=124022460014812&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13156
Subject		: keyboard backlight brightness up/down keys doesn't work
Submitter	: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Date		: 2009-04-23 20:46 (24 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13148
Subject		: resume after suspend-to-ram broken on Sony Vaio VGN-SR19VN when sony-laptop driver present
Submitter	: fanderay <fanderay4-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date		: 2009-04-22 14:39 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-15 12:43 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13119
Subject		: Trouble with make-install from a NFS mount
Submitter	: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-14 21:32 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=123974482327044&w=4
Handled-By	: H. Peter Anvin <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
Submitter	: Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-10 16:05 (37 days old)
References	: http://lkml.org/lkml/2009/4/10/111
		  http://lkml.org/lkml/2009/4/25/83
Handled-By	: Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
Subject		: Can't boot with nosmp
Submitter	: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-15 4:18 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
Handled-By	: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Date		: 2009-04-09 15:43 (38 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
		  http://lkml.org/lkml/2009/4/10/193
Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13069
Subject		: regression in 2.6.29-git3 on SH/Dreamcast
Submitter	: Adrian McMenamin <adrian-TSF8l6Tg6afpT6hvJLqO3U8SxdOydiOw@public.gmane.org>
Date		: 2009-03-29 19:04 (49 days old)
References	: http://marc.info/?l=linux-kernel&m=123835353115372&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
Subject		: Lockdep warining in inotify_dev_queue_event
Submitter	: Sachin Sant <sachinp-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-05 12:37 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13125
Subject		: active uvcvideo breaks over suspend
Submitter	: Alan Jenkins <alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
Date		: 2009-04-15 10:12 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979009508840&w=4
Handled-By	: Ming Lei <tom.leiming-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/4/18/5


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-16 19:23 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
Handled-By	: Jeff Mahoney <jeffm-IBi9RG/b67k@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/5/10/91


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13109
Subject		: High latency on /sys/class/thermal
Submitter	: Tiago Simões Batista <tiagosbatista-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-11 14:56 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123946182301248&w=4
Handled-By	: Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
		  Alexey Starikovskiy <astarikovskiy-l3A5Bk7waGM@public.gmane.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21061
		  http://bugzilla.kernel.org/attachment.cgi?id=21282


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

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

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

Thanks,
Rafael

[Bug #13068] Lockdep warining in inotify_dev_queue_event

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
Subject		: Lockdep warining in inotify_dev_queue_event
Submitter	: Sachin Sant <sachinp@in.ibm.com>
Date		: 2009-04-05 12:37 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

[Bug #13068] Lockdep warining in inotify_dev_queue_event

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
Subject		: Lockdep warining in inotify_dev_queue_event
Submitter	: Sachin Sant <sachinp-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-05 12:37 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

[Bug #13069] regression in 2.6.29-git3 on SH/Dreamcast

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13069
Subject		: regression in 2.6.29-git3 on SH/Dreamcast
Submitter	: Adrian McMenamin <adrian@newgolddream.dyndns.info>
Date		: 2009-03-29 19:04 (49 days old)
References	: http://marc.info/?l=linux-kernel&m=123835353115372&w=4

[Bug #13069] regression in 2.6.29-git3 on SH/Dreamcast

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13069
Subject		: regression in 2.6.29-git3 on SH/Dreamcast
Submitter	: Adrian McMenamin <adrian-TSF8l6Tg6afpT6hvJLqO3U8SxdOydiOw@public.gmane.org>
Date		: 2009-03-29 19:04 (49 days old)
References	: http://marc.info/?l=linux-kernel&m=123835353115372&w=4

[Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
Submitter	: Kumar Gala <galak@kernel.crashing.org>
Date		: 2009-04-09 15:43 (38 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
		  http://lkml.org/lkml/2009/4/10/193
Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

[Bug #13118] iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
Date		: 2009-04-10 16:05 (37 days old)
References	: http://lkml.org/lkml/2009/4/10/111
		  http://lkml.org/lkml/2009/4/25/83
Handled-By	: Eric Dumazet <dada1@cosmosbay.com>

[Bug #13109] High latency on /sys/class/thermal

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13109
Subject		: High latency on /sys/class/thermal
Submitter	: Tiago Simões Batista <tiagosbatista@gmail.com>
Date		: 2009-04-11 14:56 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123946182301248&w=4
Handled-By	: Zhang Rui <rui.zhang@intel.com>
		  Alexey Starikovskiy <astarikovskiy@suse.de>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21061
		  http://bugzilla.kernel.org/attachment.cgi?id=21282

[Bug #13116] Can't boot with nosmp

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
Subject		: Can't boot with nosmp
Submitter	: Stephen Hemminger <shemminger@vyatta.com>
Date		: 2009-04-15 4:18 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
Handled-By	: Dan Williams <dan.j.williams@intel.com>

[Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Date		: 2009-04-09 15:43 (38 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
		  http://lkml.org/lkml/2009/4/10/193
Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

[Bug #13118] iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
Submitter	: Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-10 16:05 (37 days old)
References	: http://lkml.org/lkml/2009/4/10/111
		  http://lkml.org/lkml/2009/4/25/83
Handled-By	: Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>

[Bug #13116] Can't boot with nosmp

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
Subject		: Can't boot with nosmp
Submitter	: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-15 4:18 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
Handled-By	: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

[Bug #13109] High latency on /sys/class/thermal

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13109
Subject		: High latency on /sys/class/thermal
Submitter	: Tiago Simões Batista <tiagosbatista-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-11 14:56 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123946182301248&w=4
Handled-By	: Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
		  Alexey Starikovskiy <astarikovskiy-l3A5Bk7waGM@public.gmane.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21061
		  http://bugzilla.kernel.org/attachment.cgi?id=21282

[Bug #13119] Trouble with make-install from a NFS mount

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13119
Subject		: Trouble with make-install from a NFS mount
Submitter	: Gregory Haskins <ghaskins@novell.com>
Date		: 2009-04-14 21:32 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=123974482327044&w=4
Handled-By	: H. Peter Anvin <hpa@zytor.com>

[Bug #13122] reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2009-04-16 19:23 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
Handled-By	: Jeff Mahoney <jeffm@suse.com>
Patch		: http://lkml.org/lkml/2009/5/10/91

[Bug #13125] active uvcvideo breaks over suspend

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13125
Subject		: active uvcvideo breaks over suspend
Submitter	: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Date		: 2009-04-15 10:12 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979009508840&w=4
Handled-By	: Ming Lei <tom.leiming@gmail.com>
Patch		: http://lkml.org/lkml/2009/4/18/5

[Bug #13119] Trouble with make-install from a NFS mount

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13119
Subject		: Trouble with make-install from a NFS mount
Submitter	: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-14 21:32 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=123974482327044&w=4
Handled-By	: H. Peter Anvin <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>

[Bug #13122] reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-16 19:23 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
Handled-By	: Jeff Mahoney <jeffm-IBi9RG/b67k@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/5/10/91

[Bug #13125] active uvcvideo breaks over suspend

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13125
Subject		: active uvcvideo breaks over suspend
Submitter	: Alan Jenkins <alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
Date		: 2009-04-15 10:12 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979009508840&w=4
Handled-By	: Ming Lei <tom.leiming-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/4/18/5

[Bug #13156] keyboard backlight brightness up/down keys doesn't work

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13156
Subject		: keyboard backlight brightness up/down keys doesn't work
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2009-04-23 20:46 (24 days old)

[Bug #13148] resume after suspend-to-ram broken on Sony Vaio VGN-SR19VN when sony-laptop driver present

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13148
Subject		: resume after suspend-to-ram broken on Sony Vaio VGN-SR19VN when sony-laptop driver present
Submitter	: fanderay <fanderay4@googlemail.com>
Date		: 2009-04-22 14:39 (25 days old)

[Bug #13126] BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2009-04-15 12:43 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4

[Bug #13148] resume after suspend-to-ram broken on Sony Vaio VGN-SR19VN when sony-laptop driver present

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13148
Subject		: resume after suspend-to-ram broken on Sony Vaio VGN-SR19VN when sony-laptop driver present
Submitter	: fanderay <fanderay4-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Date		: 2009-04-22 14:39 (25 days old)

[Bug #13126] BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-15 12:43 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4

[Bug #13156] keyboard backlight brightness up/down keys doesn't work

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13156
Subject		: keyboard backlight brightness up/down keys doesn't work
Submitter	: Thomas Meyer <thomas-VsYtu1Qij5c@public.gmane.org>
Date		: 2009-04-23 20:46 (24 days old)

[Bug #13171] 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13171
Subject		: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
Submitter	: Alex Bennee <kernel-hacker@bennee.com>
Date		: 2009-04-19 6:27 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=124022460014812&w=4

[Bug #13179] CD-R: wodim intermittent failures

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13179
Subject		: CD-R: wodim intermittent failures
Submitter	: Andy Isaacson <adi@hexapodia.org>
Date		: 2009-04-21 1:52 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124027879214231&w=4

[Bug #13180] 2.6.30-rc2: WARNING at i915_gem.c for i915_gem_idle

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13180
Subject		: 2.6.30-rc2: WARNING at i915_gem.c for i915_gem_idle
Submitter	: Niel Lambrechts <niel.lambrechts@gmail.com>
Date		: 2009-04-21 21:35 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124034980819102&w=4
		  http://lkml.org/lkml/2009/4/27/290

[Bug #13177] 2.6.30-rc2-git7 build problem

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
Subject		: 2.6.30-rc2-git7 build problem
Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
Date		: 2009-04-21 13:39 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
		  http://lkml.org/lkml/2009/4/27/56

[Bug #13171] 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13171
Subject		: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
Submitter	: Alex Bennee <kernel-hacker-jriKODhXDevQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-19 6:27 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=124022460014812&w=4

[Bug #13180] 2.6.30-rc2: WARNING at i915_gem.c for i915_gem_idle

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13180
Subject		: 2.6.30-rc2: WARNING at i915_gem.c for i915_gem_idle
Submitter	: Niel Lambrechts <niel.lambrechts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-21 21:35 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124034980819102&w=4
		  http://lkml.org/lkml/2009/4/27/290

[Bug #13179] CD-R: wodim intermittent failures

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13179
Subject		: CD-R: wodim intermittent failures
Submitter	: Andy Isaacson <adi-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
Date		: 2009-04-21 1:52 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124027879214231&w=4

[Bug #13177] 2.6.30-rc2-git7 build problem

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
Subject		: 2.6.30-rc2-git7 build problem
Submitter	: Martin Knoblauch <spamtrap-Ys4E+72pFW0hFhg+JK9F0w@public.gmane.org>
Date		: 2009-04-21 13:39 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
		  http://lkml.org/lkml/2009/4/27/56

[Bug #13245] possible circular locking dependency detected

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
Subject		: possible circular locking dependency detected
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2009-05-04 16:56 (13 days old)

[Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
Subject		: horizontal strips of the screen frozen
Submitter	: Justin Madru <jdm64@gawab.com>
Date		: 2009-04-24 20:59 (23 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4

[Bug #13245] possible circular locking dependency detected

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
Subject		: possible circular locking dependency detected
Submitter	: Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-04 16:56 (13 days old)

[Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
Subject		: horizontal strips of the screen frozen
Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-24 20:59 (23 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4

[Bug #13250] Side channel of Intel HDA chip doesn't work anymore, did work with 2.6.29

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13250
Subject		: Side channel of Intel HDA chip doesn't work anymore, did work with 2.6.29
Submitter	: Andreas Juch <kernel-bt@juch.cc>
Date		: 2009-05-05 10:14 (12 days old)

[Bug #13285] INTELFB: Colors display incorrectly

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13285
Subject		: INTELFB: Colors display incorrectly
Submitter	: Dean Menezes <samanddeanus@yahoo.com>
Date		: 2009-05-12 01:40 (5 days old)

[Bug #13293] Kernel BUG under network load with gianfar

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13293
Subject		: Kernel BUG under network load with gianfar
Submitter	: Michael Guntsche <mike@it-loops.com>
Date		: 2009-05-03 13:36 (14 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0fd56bb5be6455d0d42241e65aed057244665e5e
References	: http://marc.info/?l=linux-kernel&m=124135824600924&w=4

[Bug #13250] Side channel of Intel HDA chip doesn't work anymore, did work with 2.6.29

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13250
Subject		: Side channel of Intel HDA chip doesn't work anymore, did work with 2.6.29
Submitter	: Andreas Juch <kernel-bt-Sk8biX5uX1I@public.gmane.org>
Date		: 2009-05-05 10:14 (12 days old)

[Bug #13285] INTELFB: Colors display incorrectly

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13285
Subject		: INTELFB: Colors display incorrectly
Submitter	: Dean Menezes <samanddeanus-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-12 01:40 (5 days old)

[Bug #13293] Kernel BUG under network load with gianfar

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13293
Subject		: Kernel BUG under network load with gianfar
Submitter	: Michael Guntsche <mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
Date		: 2009-05-03 13:36 (14 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0fd56bb5be6455d0d42241e65aed057244665e5e
References	: http://marc.info/?l=linux-kernel&m=124135824600924&w=4

[Bug #13294] i915: drm: xorg leaks drm objects massively

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13294
Subject		: i915: drm: xorg leaks drm objects massively
Submitter	: Sergei Trofimovich <slyich@gmail.com>
Date		: 2009-05-10 19:56 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124198547027903&w=4

[Bug #13297] kernel panic - not syncing : fatel exception in interupt

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
Subject		: kernel panic -  not syncing : fatel exception in interupt
Submitter	: rob <rob1@housetosell.net>
Date		: 2009-05-12 19:34 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

[Bug #13296] Lockdep violation at cleanup_workqueue_thread during suspend

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2009-05-12 7:59 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4

[Bug #13294] i915: drm: xorg leaks drm objects massively

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13294
Subject		: i915: drm: xorg leaks drm objects massively
Submitter	: Sergei Trofimovich <slyich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-10 19:56 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124198547027903&w=4

[Bug #13296] Lockdep violation at cleanup_workqueue_thread during suspend

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
Submitter	: Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-12 7:59 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4

[Bug #13297] kernel panic - not syncing : fatel exception in interupt

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
Subject		: kernel panic -  not syncing : fatel exception in interupt
Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
Date		: 2009-05-12 19:34 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

[Bug #13298] modprobe ipmi_si hangs under 2.6.30-rc5

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
Submitter	: Ferenc Wagner <wferi@niif.hu>
Date		: 2009-05-12 21:28 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4

[Bug #13306] hibernate slow on _second_ run

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13306
Subject		: hibernate slow on _second_ run
Submitter	: Johannes Berg <johannes@sipsolutions.net>
Date		: 2009-05-14 09:34 (3 days old)

[Bug #13306] hibernate slow on _second_ run

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13306
Subject		: hibernate slow on _second_ run
Submitter	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Date		: 2009-05-14 09:34 (3 days old)

[Bug #13298] modprobe ipmi_si hangs under 2.6.30-rc5

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
Submitter	: Ferenc Wagner <wferi-eEbw3PyuezQ@public.gmane.org>
Date		: 2009-05-12 21:28 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4

[Bug #13318] AGP doesn't work anymore on nforce2

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13318
Subject		: AGP doesn't work anymore on nforce2
Submitter	: Karsten Mehrhoff <kawime@gmx.de>
Date		: 2009-04-30 8:51 (17 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=59de2bebabc5027f93df999d59cc65df591c3e6e
References	: http://marc.info/?l=linux-kernel&m=124108156417560&w=4
Handled-By	: Shaohua Li <shaohua.li@intel.com>

[Bug #13319] Page allocation failures with b43 and p54usb

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
Subject		: Page allocation failures with b43 and p54usb
Submitter	: Larry Finger <Larry.Finger@lwfinger.net>
Date		: 2009-04-29 21:01 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
Handled-By	: Johannes Berg <johannes@sipsolutions.net>

[Bug #13318] AGP doesn't work anymore on nforce2

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13318
Subject		: AGP doesn't work anymore on nforce2
Submitter	: Karsten Mehrhoff <kawime-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-04-30 8:51 (17 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=59de2bebabc5027f93df999d59cc65df591c3e6e
References	: http://marc.info/?l=linux-kernel&m=124108156417560&w=4
Handled-By	: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

[Bug #13319] Page allocation failures with b43 and p54usb

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
Subject		: Page allocation failures with b43 and p54usb
Submitter	: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Date		: 2009-04-29 21:01 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
Handled-By	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

[Bug #13324] panic when loading oprofile

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13324
Subject		: panic when loading oprofile
Submitter	: Brandeburg, Jesse <jesse.brandeburg@intel.com>
Date		: 2009-05-13 22:30 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124225384311631&w=4

[Bug #13323] 2.6.30-rc deadline scheduler performance regression for iozone over NFS

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13323
Subject		: 2.6.30-rc deadline scheduler performance regression for iozone over NFS
Submitter	: Jeff Moyer <jmoyer@redhat.com>
Date		: 2009-04-23 14:01 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124049547915450&w=4

[Bug #13321] kernel crash with NULL pointer when boot

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
Subject		: kernel crash with NULL pointer when boot
Submitter	: Martin Bammer <mrb74@gmx.at>
Date		: 2009-05-16 12:37 (1 days old)
References	: http://lkml.org/lkml/2009/5/16/100

[Bug #13324] panic when loading oprofile

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13324
Subject		: panic when loading oprofile
Submitter	: Brandeburg, Jesse <jesse.brandeburg-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-13 22:30 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124225384311631&w=4

[Bug #13321] kernel crash with NULL pointer when boot

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
Subject		: kernel crash with NULL pointer when boot
Submitter	: Martin Bammer <mrb74-RbZlAiThDcE@public.gmane.org>
Date		: 2009-05-16 12:37 (1 days old)
References	: http://lkml.org/lkml/2009/5/16/100

[Bug #13323] 2.6.30-rc deadline scheduler performance regression for iozone over NFS

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13323
Subject		: 2.6.30-rc deadline scheduler performance regression for iozone over NFS
Submitter	: Jeff Moyer <jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-23 14:01 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124049547915450&w=4

[Bug #13326] Null pointer dereference in rtc-cmos driver

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13326
Subject		: Null pointer dereference in rtc-cmos driver
Submitter	: Ozan Çağlayan <ozan@pardus.org.tr>
Date		: 2009-05-14 16:16 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231783704696&w=4

[Bug #13327] Regression: 2.6.30-rc5 and rt2x00 / rt2500pci

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13327
Subject		: Regression: 2.6.30-rc5 and rt2x00 / rt2500pci
Submitter	: Ken Lewis <kennylewis@gmail.com>
Date		: 2009-05-15 14:40 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=124239988223614&w=4
Handled-By	: John W. Linville <linville@tuxdriver.com>

[Bug #13325] 2.6.30-rc kills my box hard - and lockdep chains

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
Subject		: 2.6.30-rc kills my box hard - and lockdep chains
Submitter	: Jonathan Corbet <corbet@lwn.net>
Date		: 2009-05-14 15:49 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4

[Bug #13326] Null pointer dereference in rtc-cmos driver

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13326
Subject		: Null pointer dereference in rtc-cmos driver
Submitter	: Ozan Çağlayan <ozan-caicS1wCkhO6A22drWdTBw@public.gmane.org>
Date		: 2009-05-14 16:16 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231783704696&w=4

[Bug #13327] Regression: 2.6.30-rc5 and rt2x00 / rt2500pci

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13327
Subject		: Regression: 2.6.30-rc5 and rt2x00 / rt2500pci
Submitter	: Ken Lewis <kennylewis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-15 14:40 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=124239988223614&w=4
Handled-By	: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

[Bug #13325] 2.6.30-rc kills my box hard - and lockdep chains

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
Subject		: 2.6.30-rc kills my box hard - and lockdep chains
Submitter	: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>
Date		: 2009-05-14 15:49 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4

[Bug #13328] b44: eth0: BUG! Timeout waiting for bit 00000002 of register 42c to clear.

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13328
Subject		: b44: eth0: BUG! Timeout waiting for bit 00000002 of register 42c to clear.
Submitter	: Francis Moreau <francis.moro@gmail.com>
Date		: 2009-05-03 16:22 (14 days old)
References	: http://marc.info/?l=linux-kernel&m=124136778012280&w=4

[Bug #13329] cifs_close: NULL pointer dereference

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
Subject		: cifs_close: NULL pointer dereference
Submitter	: Luca Tettamanti <kronos.it@gmail.com>
Date		: 2009-05-16 16:28 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4

[Bug #13329] cifs_close: NULL pointer dereference

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
Subject		: cifs_close: NULL pointer dereference
Submitter	: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-05-16 16:28 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4

Re: [Bug #13179] CD-R: wodim intermittent failures

[Robert Hancock]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13179
> Subject		: CD-R: wodim intermittent failures
> Submitter	: Andy Isaacson <adi@hexapodia.org>
> Date		: 2009-04-21 1:52 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=124027879214231&w=4

Last I heard the reporter was going to attempt to bisect the problem to 
see when the spurious udev events he was seeing started happening..

Re: [Bug #13179] CD-R: wodim intermittent failures

[Robert Hancock]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13179
> Subject		: CD-R: wodim intermittent failures
> Submitter	: Andy Isaacson <adi-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
> Date		: 2009-04-21 1:52 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=124027879214231&w=4

Last I heard the reporter was going to attempt to bisect the problem to 
see when the spurious udev events he was seeing started happening..

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Andrew Morton]

On Sat, 16 May 2009 21:20:45 +0200 (CEST) "Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
> Subject		: Page allocation failures with b43 and p54usb
> Submitter	: Larry Finger <Larry.Finger@lwfinger.net>
> Date		: 2009-04-29 21:01 (18 days old)
> References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
> Handled-By	: Johannes Berg <johannes@sipsolutions.net>
> 
> 

Well..  order-1 GFP_ATOMIC allocations are unreliable.  The networking
code should hanlde the situation and recover.  I assume that is
happening in this case?

Perhaps we did something in that code after 2.6.29 which increased the
frequency of the order-1 allocation attempts?  Maybe earlier kernels
used order-0 all the time?  Those are much more reliable.

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Andrew Morton]

On Sat, 16 May 2009 21:20:45 +0200 (CEST) "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
> Subject		: Page allocation failures with b43 and p54usb
> Submitter	: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
> Date		: 2009-04-29 21:01 (18 days old)
> References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
> Handled-By	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> 
> 

Well..  order-1 GFP_ATOMIC allocations are unreliable.  The networking
code should hanlde the situation and recover.  I assume that is
happening in this case?

Perhaps we did something in that code after 2.6.29 which increased the
frequency of the order-1 allocation attempts?  Maybe earlier kernels
used order-0 all the time?  Those are much more reliable.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
> Subject		: cifs_close: NULL pointer dereference
> Submitter	: Luca Tettamanti <kronos.it@gmail.com>
> Date		: 2009-05-16 16:28 (1 days old)
> References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4

The code in this one decodes to

   0:	89 ef                	mov    %ebp,%edi
   2:	45 31 e4             	xor    %r12d,%r12d
   5:	e8 f3 63 e7 df       	callq  0xffffffffdfe763fd
   a:	41 bd 0a 00 00 00    	mov    $0xa,%r13d
  10:	48 c7 c7 c4 6b 61 a0 	mov    $0xffffffffa0616bc4,%rdi
  17:	e8 b3 7f e7 df       	callq  0xffffffffdfe77fcf
  1c:	48 8b 53 10          	mov    0x10(%rbx),%rdx
  20:	48 8b 43 18          	mov    0x18(%rbx),%rax
  24:	48 c7 c7 c4 6b 61 a0 	mov    $0xffffffffa0616bc4,%rdi
  2b:*	48 89 42 08          	mov    %rax,0x8(%rdx)     <-- trapping instruction
  2f:	48 89 10             	mov    %rdx,(%rax)
  32:	48 c7 43 18 00 02 20 	movq   $0x200200,0x18(%rbx)
  39:	00 
  3a:	48 8b 13             	mov    (%rbx),%rdx

which seems to match (modulo normal compiler issues):

        movq    -56(%rbp), %rdi # %sfp,
        call    mutex_unlock    #
        movq    $GlobalSMBSeslock, %rdi #,
        call    _write_lock     #
        movq    16(%rbx), %rdx  # <variable>.flist.next, D.47095
        movq    24(%rbx), %rax  # <variable>.flist.prev, D.47094
        movq    %rax, 8(%rdx)   # D.47094, <variable>.prev
        movq    %rdx, (%rax)    # D.47095, <variable>.next
        movq    $2097664, 24(%rbx)      #, <variable>.flist.prev
        movq    (%rbx), %rdx    # <variable>.tlist.next, D.47099

which I think ends up being this code:

                mutex_unlock(&pSMBFile->lock_mutex);
        
                write_lock(&GlobalSMBSeslock);
                list_del(&pSMBFile->flist);   

ie 'pSMBFile->flist.next' looks to be zero. Either uninitialized or 
perhaps a use-after-free thing..

We have commit 90e4ee5d31 "[CIFS] Fix double list addition in cifs posix 
open code" that touches exactly that 'flist' thing, and removes the thing 
that adds it to the list because it's _claimed_ to be a "double add". It 
probably wasn't.

The bug reporter says:

> The machine is running kernel from git (1d80cac - almost rc6)

and that 1d80cac is _after_ 90e4ee5d31. So I do think 90e4ee5d31 is buggy.

		Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13326
> Subject		: Null pointer dereference in rtc-cmos driver
> Submitter	: Ozan Çağlayan <ozan@pardus.org.tr>
> Date		: 2009-05-14 16:16 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124231783704696&w=4

Ok, I'm of two minds on this one.

The thing that triggers it is a module that is both a module _and_ 
compiled in (ie the same kernel compiled twice, and the stale module kept 
around). I can see how it happens, and we should react more gracefully to 
it, but at the same time I can't really bring myself to care deeply.

What is going on is that the cmos-rtc.c driver does this:

	#ifdef  CONFIG_PNP
	        pnp_register_driver(&cmos_pnp_driver);
	#endif

	        if (!cmos_rtc.dev)
	                retval = platform_driver_probe(&cmos_platform_driver,
                                               cmos_platform_probe);

	        if (retval == 0)
	                return 0;

	#ifdef  CONFIG_PNP
	        pnp_unregister_driver(&cmos_pnp_driver);
	#endif
	        return retval;

and what happens is that the pnp_register_driver fails when the module 
calls it (because the built-in driver already exists under the same name):

	[   10.428691] Error: Driver 'rtc_cmos' is already registered, aborting...

but the driver doesn't really care whether that succeeded or not, but then 
the platform_driver_probe fails (because the thing is already in use), so 
then it ends up unregistering something that never got registered in the 
first place.

I think this is strictly speaking a bug in driver_unregister(), which is 
too fragile. If you unregister a drivert that wasn't registered, we 
shouldn't oops. 

But we could certainly do it at the rtc-cmos.c level too, and just not 
unregister it if the registration failed. My gut feel is that we should 
aim for the core driver helpers to be less fragile, though - we'll always 
have driver bugs.

Greg?

			Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Kay Sievers]

On Sun, May 17, 2009 at 02:01, Linus Torvalds
<torvalds@linux-foundation.org> wrote:

>        [   10.428691] Error: Driver 'rtc_cmos' is already registered, aborting...
>
> but the driver doesn't really care whether that succeeded or not, but then
> the platform_driver_probe fails (because the thing is already in use), so
> then it ends up unregistering something that never got registered in the
> first place.
>
> I think this is strictly speaking a bug in driver_unregister(), which is
> too fragile. If you unregister a drivert that wasn't registered, we
> shouldn't oops.
>
> But we could certainly do it at the rtc-cmos.c level too, and just not
> unregister it if the registration failed. My gut feel is that we should
> aim for the core driver helpers to be less fragile, though - we'll always
> have driver bugs.

In:
 driver_remove_file()
we try to access the private part:
 sysfs_remove_file(&drv->p->kobj, ...
and that is NULL, for an unregistered driver, I would expect.

I'm looking into it.

Kay

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ozan Çağlayan]

Linus Torvalds wrote:
>
> Ok, I'm of two minds on this one.
>
> The thing that triggers it is a module that is both a module _and_ 
> compiled in (ie the same kernel compiled twice, and the stale module kept 
> around). I can see how it happens, and we should react more gracefully to 
> it, but at the same time I can't really bring myself to care deeply.
>   

The patch[0] from Andrew fixed the problem.

Thanks,
Ozan Caglayan

[0]: http://marc.info/?l=linux-kernel&m=124251428228049&w=2

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Kay Sievers]

On Sun, 2009-05-17 at 02:15 +0200, Kay Sievers wrote:
> On Sun, May 17, 2009 at 02:01, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> 
> >        [   10.428691] Error: Driver 'rtc_cmos' is already registered, aborting...
> >
> > but the driver doesn't really care whether that succeeded or not, but then
> > the platform_driver_probe fails (because the thing is already in use), so
> > then it ends up unregistering something that never got registered in the
> > first place.
> >
> > I think this is strictly speaking a bug in driver_unregister(), which is
> > too fragile. If you unregister a drivert that wasn't registered, we
> > shouldn't oops.
> >
> > But we could certainly do it at the rtc-cmos.c level too, and just not
> > unregister it if the registration failed. My gut feel is that we should
> > aim for the core driver helpers to be less fragile, though - we'll always
> > have driver bugs.
> 
> In:
>  driver_remove_file()
> we try to access the private part:
>  sysfs_remove_file(&drv->p->kobj, ...
> and that is NULL, for an unregistered driver, I would expect.
> 
> I'm looking into it.

This makes the oops in the driver-core, caused by the rtc driver
unregister, go away. The original issue is also fixed in the rtc driver
itself.

Thanks,
Kay


From: Kay Sievers <kay.sievers@vrfy.org>
Subject: Driver Core: do not oops when driver_unregister() is called for unregistered drivers

Handle the case someone tries to unregister a non-registered driver
more gracefully.

  Error: Driver 'rtc_cmos' is already registered, aborting...
  BUG: unable to handle kernel NULL pointer dereference at 00000018
  [<c01e16ba>] sysfs_remove_file+0x1/0xf

Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
---

 driver.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -257,6 +257,8 @@ EXPORT_SYMBOL_GPL(driver_register);
  */
 void driver_unregister(struct device_driver *drv)
 {
+	if (!drv || !drv->p)
+		return;
 	driver_remove_groups(drv, drv->groups);
 	bus_remove_driver(drv);
 }

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Sun, 17 May 2009, Ozan Çağlayan wrote:
> 
> The patch[0] from Andrew fixed the problem.

Yeah, but that's the patch that I think isn't the long-term solution (ie 
other drievrs will do things like this too).

Also, I'm not 100% convinced it's even the right one for cmos-rtc, 
although I can't really judge. The thing is, even if the 
pnp_register_driver() call fails, I'm not at all sure that we shouldn't 
just continue. I suspect we might still want to do the 
platform_driver_probe regardless of any PnP issues.

I dunno. What I _do_ know is that I'd be happier of 

	pnp_register_driver(&driver);
	pnp_unregister_driver(&driver);

always worked without oopsing, regardless of whether the registration 
worked or not. Whether the rtc-cmos driver shold do that is then a 
secondary issue. 

The whole PnP thing has been broken several times, look for example at 
commit 72f22b1eb6ca5e4676a632a04d40d46cb61d4562. That one introduced the 
whole "do the platform driver regardless of any PnP driver issues", which 
makes me suspect we really shouldn't return early just because of some 
random pnp issue.

			Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Sun, 17 May 2009, Kay Sievers wrote:
> 
> This makes the oops in the driver-core, caused by the rtc driver
> unregister, go away. The original issue is also fixed in the rtc driver
> itself.

I don't think this is sufficient.

> --- a/drivers/base/driver.c
> +++ b/drivers/base/driver.c
> @@ -257,6 +257,8 @@ EXPORT_SYMBOL_GPL(driver_register);
>   */
>  void driver_unregister(struct device_driver *drv)
>  {
> +	if (!drv || !drv->p)
> +		return;
>  	driver_remove_groups(drv, drv->groups);
>  	bus_remove_driver(drv);
>  }

Ok, fine so far, but look at "driver_register()".

It will set drv->p, but then not unset it if it fails! (For a certain 
class of failures)

So for a certain failure pattern, drv->p will point to some stale value. 
Should we not clear drv->p in the "out_unregister" patch?

To confuse the thing more, there are actually "half-way failures" that 
_succeed_ in driver registration, but then return an error code. See that 
whole


	kobject_uevent(&priv->kobj, KOBJ_ADD);
	return error;

case in the "success" path driver_register(). We may return an error 
despite the fact that we actually attached the driver to bus, but 
"add_bind_files()" failed. A caller would be understandable very unhappy.

So I suspect we should do something like the appended (in addition to your 
patch). Comments?

			Linus
---

 drivers/base/bus.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/drivers/base/bus.c b/drivers/base/bus.c
index dc030f1..dcd499d 100644
--- a/drivers/base/bus.c
+++ b/drivers/base/bus.c
@@ -700,8 +700,9 @@ int bus_add_driver(struct device_driver *drv)
 	}
 
 	kobject_uevent(&priv->kobj, KOBJ_ADD);
-	return error;
+	return 0;
 out_unregister:
+	drv->p = NULL;
 	kobject_put(&priv->kobj);
 out_put_bus:
 	bus_put(bus);

Re: [Bug #13245] possible circular locking dependency detected

[Ming Lei]

I also can reproduce it on 2.6.30-rc5-next-20090515.

2009/5/17 Rafael J. Wysocki <rjw@sisk.pl>:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13245
> Subject         : possible circular locking dependency detected
> Submitter       : Miles Lane <miles.lane@gmail.com>
> Date            : 2009-05-04 16:56 (13 days old)
>

-- 
Lei Ming

Re: [Bug #13118] iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

[Jeff Chua]

On Sun, May 17, 2009 at 3:20 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13118
> Subject         : iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> Date            : 2009-04-10 16:05 (37 days old)
> References      : http://lkml.org/lkml/2009/4/10/111
>                  http://lkml.org/lkml/2009/4/25/83
> Handled-By      : Eric Dumazet <dada1@cosmosbay.com>

Fixed as of Apr 28.

commit 942e4a2bd680c606af0211e64eb216be2e19bf61
Author: Stephen Hemminger <shemminger@vyatta.com>
Date:   Tue Apr 28 22:36:33 2009 -0700

    netfilter: revised locking for x_tables


Thanks,
Jeff.

Re: [Bug #13118] iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

[Jeff Chua]

On Sun, May 17, 2009 at 3:20 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13118
> Subject         : iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> Submitter       : Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date            : 2009-04-10 16:05 (37 days old)
> References      : http://lkml.org/lkml/2009/4/10/111
>                  http://lkml.org/lkml/2009/4/25/83
> Handled-By      : Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>

Fixed as of Apr 28.

commit 942e4a2bd680c606af0211e64eb216be2e19bf61
Author: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
Date:   Tue Apr 28 22:36:33 2009 -0700

    netfilter: revised locking for x_tables


Thanks,
Jeff.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Kay Sievers <kay.sievers@vrfy.org> wrote:

> On Sun, 2009-05-17 at 02:15 +0200, Kay Sievers wrote:
> > On Sun, May 17, 2009 at 02:01, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > 
> > >        [   10.428691] Error: Driver 'rtc_cmos' is already registered, aborting...
> > >
> > > but the driver doesn't really care whether that succeeded or not, but then
> > > the platform_driver_probe fails (because the thing is already in use), so
> > > then it ends up unregistering something that never got registered in the
> > > first place.
> > >
> > > I think this is strictly speaking a bug in driver_unregister(), which is
> > > too fragile. If you unregister a drivert that wasn't registered, we
> > > shouldn't oops.
> > >
> > > But we could certainly do it at the rtc-cmos.c level too, and just not
> > > unregister it if the registration failed. My gut feel is that we should
> > > aim for the core driver helpers to be less fragile, though - we'll always
> > > have driver bugs.
> > 
> > In:
> >  driver_remove_file()
> > we try to access the private part:
> >  sysfs_remove_file(&drv->p->kobj, ...
> > and that is NULL, for an unregistered driver, I would expect.
> > 
> > I'm looking into it.
> 
> This makes the oops in the driver-core, caused by the rtc driver
> unregister, go away. The original issue is also fixed in the rtc driver
> itself.
> 
> Thanks,
> Kay
> 
> 
> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: Driver Core: do not oops when driver_unregister() is called for unregistered drivers
> 
> Handle the case someone tries to unregister a non-registered driver
> more gracefully.
> 
>   Error: Driver 'rtc_cmos' is already registered, aborting...
>   BUG: unable to handle kernel NULL pointer dereference at 00000018
>   [<c01e16ba>] sysfs_remove_file+0x1/0xf
> 
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>

please also put in a proper Reported-by.

> ---
> 
>  driver.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- a/drivers/base/driver.c
> +++ b/drivers/base/driver.c
> @@ -257,6 +257,8 @@ EXPORT_SYMBOL_GPL(driver_register);
>   */
>  void driver_unregister(struct device_driver *drv)
>  {
> +	if (!drv || !drv->p)
> +		return;

I think it would be reasonable to also emit a:

	 WARN_ONCE(1, "unexpected driver unregister!\n");

here - as long as all such cases are a bug. As the imbalance (and a 
bug) is really at the rtc-cmos driver level too and we should not 
condone such pattern, silently.

( Not crashing in the driver core when we can avoid it is nice to 
  have too, of course. )

	Ingo

Re: [Bug #13068] Lockdep warining in inotify_dev_queue_event

[Ingo Molnar]

* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> Subject		: Lockdep warining in inotify_dev_queue_event

s/warining/warning

> Submitter	: Sachin Sant <sachinp@in.ibm.com>
> Date		: 2009-04-05 12:37 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

i think this might be fixed by:

381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

already in -rc6.

	Ingo

Re: [Bug #13068] Lockdep warining in inotify_dev_queue_event

[Ingo Molnar]

* Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> Subject		: Lockdep warining in inotify_dev_queue_event

s/warining/warning

> Submitter	: Sachin Sant <sachinp-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
> Date		: 2009-04-05 12:37 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

i think this might be fixed by:

381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

already in -rc6.

	Ingo

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> Submitter	: Jonathan Corbet <corbet@lwn.net>
> Date		: 2009-05-14 15:49 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4

Jonathan, there's a side-issue reported there, us running out of 
lockdep space. Could you try this commit from -tip:

d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS

(which i'll get to Linus in the next ~24 hours.) Maybe that allows 
lockdep to report the reason for the deadlock.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> Subject		: kernel crash with NULL pointer when boot
> Submitter	: Martin Bammer <mrb74@gmx.at>
> Date		: 2009-05-16 12:37 (1 days old)
> References	: http://lkml.org/lkml/2009/5/16/100

that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
xattr teardown.

There's been a good deal of reiserfs changes in this cycle - some 
touch the xattr code as well. Some of them fairly late in the cycle, 
in the last two weeks:

 earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
 2a32ceb: Fix races around the access to ->s_options
 677c9b2: reiserfs: remove privroot hiding in lookup
 b82bb72: reiserfs: dont associate security.* with xattr files
 ab17c4f: reiserfs: fixup xattr_root caching
 edcc37a: Always lookup priv_root on reiserfs mount and keep it
 5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len

Martin, you could try a blind revert of say ... ab17c4f, which looks 
the most suspect and which is also a rather large commit.

Or/and you could try a bisect - perhaps accelerated via:

   git bisect start fs/reiserfs/

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> Subject		: kernel panic -  not syncing : fatel exception in interupt
> Submitter	: rob <rob1@housetosell.net>
> Date		: 2009-05-12 19:34 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

tainted crash, but probably legit. It does show some badness in an 
old-IDE legacy codepath:

[<c0371865>] error_code+0x65/0x6c
[<c0110155>] do_page_fault+0x0/0x1e0
[<c027dafc>] ide_complete_rq+0xf/0x3b
[<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
[<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
[<c027dcc2>] ide_intr+0x109/0x161
[<c0132298>] handle_IRQ_event+0x54/0xc7
[<c013354a>] handle_level_irq+0x4f/0x85
[<c0103df7>] handle_irq+0x17/0x20
[<c0103da5>] do_IRQ+0x2b/0x66
[<c0102be9>] common_interupt+0x29/0x30
[<c0480000>] cmd40x_init+0x2ac/0x38d
[<c0106db3>] default_idle+0x25/0x38
[<c01019be>] cpu_idle+0x19/0x2d
[<c0468907>] start_kernel+0x23f/0x242

report subject line is too unspecific, it should be changed to 
something like:

  legacy IDE cmd40x related bootup crash

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> Date		: 2009-05-12 7:59 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4

looks like wireless related - the dependency that connects the 
locks in a wrong way appears to be:

 -> #2 (cfg80211_mutex){+.+.+.}:
        [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
        [<ffffffff80271f38>] lock_acquire+0x98/0x140
        [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
        [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
        [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
        [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
        [<ffffffff8025dc3a>] kthread+0x5a/0xa0
        [<ffffffff8020d23a>] child_rip+0xa/0x20

(havent checked deeper)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> Subject		: possible circular locking dependency detected
> Submitter	: Miles Lane <miles.lane@gmail.com>
> Date		: 2009-05-04 16:56 (13 days old)

same as #13296 above. (The one above should be merged into this one 
i guess)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> Date		: 2009-04-15 12:43 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4

should be resolved via the lockdep space extension fix.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
> Date		: 2009-04-10 16:05 (37 days old)
> References	: http://lkml.org/lkml/2009/4/10/111
> 		  http://lkml.org/lkml/2009/4/25/83
> Handled-By	: Eric Dumazet <dada1@cosmosbay.com>

solved by:

 commit 942e4a2bd680c606af0211e64eb216be2e19bf61
 Author: Stephen Hemminger <shemminger@vyatta.com>
 Date:   Tue Apr 28 22:36:33 2009 -0700

    netfilter: revised locking for x_tables

commit log does not credit reporters and testers and does not 
mention bugzilla id.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> Subject		: Can't boot with nosmp
> Submitter	: Stephen Hemminger <shemminger@vyatta.com>
> Date		: 2009-04-15 4:18 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> Handled-By	: Dan Williams <dan.j.williams@intel.com>

I think this might be fixed by:

 d6de2c8: async: Fix module loading async-work regression

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

Oleg says in that thread that it's as-designed, and followup 
questions were not replied to (yet).

But ... a relevant seeming commit has been bisected to so this 
shouldnt be ignored that easily.

Andrew, you merged the commit that was bisected to:

  From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
  From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
  Date: Thu, 2 Apr 2009 16:58:08 -0700
  Subject: [PATCH] signals: protect cinit from blocked fatal signals

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> Subject		: Lockdep warining in inotify_dev_queue_event
> Submitter	: Sachin Sant <sachinp@in.ibm.com>
> Date		: 2009-04-05 12:37 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

should be fixed by:

381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

	Ingo

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> Submitter	: Jonathan Corbet <corbet@lwn.net>
> Date		: 2009-05-14 15:49 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4

Jonathan, there's a side-issue reported there, us running out of 
lockdep space. Could you try this commit from -tip:

d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS

(which i'll get to Linus in the next ~24 hours.) Maybe that allows 
lockdep to report the reason for the deadlock.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> Subject		: kernel crash with NULL pointer when boot
> Submitter	: Martin Bammer <mrb74@gmx.at>
> Date		: 2009-05-16 12:37 (1 days old)
> References	: http://lkml.org/lkml/2009/5/16/100

that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
xattr teardown.

There's been a good deal of reiserfs changes in this cycle - some 
touch the xattr code as well. Some of them fairly late in the cycle, 
in the last two weeks:

 earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
 2a32ceb: Fix races around the access to ->s_options
 677c9b2: reiserfs: remove privroot hiding in lookup
 b82bb72: reiserfs: dont associate security.* with xattr files
 ab17c4f: reiserfs: fixup xattr_root caching
 edcc37a: Always lookup priv_root on reiserfs mount and keep it
 5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len

Martin, you could try a blind revert of say ... ab17c4f, which looks 
the most suspect and which is also a rather large commit.

Or/and you could try a bisect - perhaps accelerated via:

   git bisect start fs/reiserfs/

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> Subject		: kernel panic -  not syncing : fatel exception in interupt
> Submitter	: rob <rob1@housetosell.net>
> Date		: 2009-05-12 19:34 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

tainted crash, but probably legit. It does show some badness in an 
old-IDE legacy codepath:

[<c0371865>] error_code+0x65/0x6c
[<c0110155>] do_page_fault+0x0/0x1e0
[<c027dafc>] ide_complete_rq+0xf/0x3b
[<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
[<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
[<c027dcc2>] ide_intr+0x109/0x161
[<c0132298>] handle_IRQ_event+0x54/0xc7
[<c013354a>] handle_level_irq+0x4f/0x85
[<c0103df7>] handle_irq+0x17/0x20
[<c0103da5>] do_IRQ+0x2b/0x66
[<c0102be9>] common_interupt+0x29/0x30
[<c0480000>] cmd40x_init+0x2ac/0x38d
[<c0106db3>] default_idle+0x25/0x38
[<c01019be>] cpu_idle+0x19/0x2d
[<c0468907>] start_kernel+0x23f/0x242

report subject line is too unspecific, it should be changed to 
something like:

  legacy IDE cmd40x related bootup crash

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> Date		: 2009-05-12 7:59 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4

looks like wireless related - the dependency that connects the 
locks in a wrong way appears to be:

 -> #2 (cfg80211_mutex){+.+.+.}:
        [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
        [<ffffffff80271f38>] lock_acquire+0x98/0x140
        [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
        [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
        [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
        [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
        [<ffffffff8025dc3a>] kthread+0x5a/0xa0
        [<ffffffff8020d23a>] child_rip+0xa/0x20

(havent checked deeper)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> Subject		: possible circular locking dependency detected
> Submitter	: Miles Lane <miles.lane@gmail.com>
> Date		: 2009-05-04 16:56 (13 days old)

same as #13296 above. (The one above should be merged into this one 
i guess)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> Date		: 2009-04-15 12:43 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4

should be resolved via the lockdep space extension fix.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
> Date		: 2009-04-10 16:05 (37 days old)
> References	: http://lkml.org/lkml/2009/4/10/111
> 		  http://lkml.org/lkml/2009/4/25/83
> Handled-By	: Eric Dumazet <dada1@cosmosbay.com>

solved by:

 commit 942e4a2bd680c606af0211e64eb216be2e19bf61
 Author: Stephen Hemminger <shemminger@vyatta.com>
 Date:   Tue Apr 28 22:36:33 2009 -0700

    netfilter: revised locking for x_tables

commit log does not credit reporters and testers and does not 
mention bugzilla id.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> Subject		: Can't boot with nosmp
> Submitter	: Stephen Hemminger <shemminger@vyatta.com>
> Date		: 2009-04-15 4:18 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> Handled-By	: Dan Williams <dan.j.williams@intel.com>

I think this might be fixed by:

 d6de2c8: async: Fix module loading async-work regression

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

Oleg says in that thread that it's as-designed, and followup 
questions were not replied to (yet).

But ... a relevant seeming commit has been bisected to so this 
shouldnt be ignored that easily.

Andrew, you merged the commit that was bisected to:

  From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
  From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
  Date: Thu, 2 Apr 2009 16:58:08 -0700
  Subject: [PATCH] signals: protect cinit from blocked fatal signals

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> Subject		: Lockdep warining in inotify_dev_queue_event
> Submitter	: Sachin Sant <sachinp@in.ibm.com>
> Date		: 2009-04-05 12:37 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

should be fixed by:

381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

	Ingo

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> Submitter	: Jonathan Corbet <corbet@lwn.net>
> Date		: 2009-05-14 15:49 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4

Jonathan, there's a side-issue reported there, us running out of 
lockdep space. Could you try this commit from -tip:

d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS

(which i'll get to Linus in the next ~24 hours.) Maybe that allows 
lockdep to report the reason for the deadlock.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> Subject		: kernel crash with NULL pointer when boot
> Submitter	: Martin Bammer <mrb74@gmx.at>
> Date		: 2009-05-16 12:37 (1 days old)
> References	: http://lkml.org/lkml/2009/5/16/100

that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
xattr teardown.

There's been a good deal of reiserfs changes in this cycle - some 
touch the xattr code as well. Some of them fairly late in the cycle, 
in the last two weeks:

 earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
 2a32ceb: Fix races around the access to ->s_options
 677c9b2: reiserfs: remove privroot hiding in lookup
 b82bb72: reiserfs: dont associate security.* with xattr files
 ab17c4f: reiserfs: fixup xattr_root caching
 edcc37a: Always lookup priv_root on reiserfs mount and keep it
 5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len

Martin, you could try a blind revert of say ... ab17c4f, which looks 
the most suspect and which is also a rather large commit.

Or/and you could try a bisect - perhaps accelerated via:

   git bisect start fs/reiserfs/

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> Subject		: kernel panic -  not syncing : fatel exception in interupt
> Submitter	: rob <rob1@housetosell.net>
> Date		: 2009-05-12 19:34 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

tainted crash, but probably legit. It does show some badness in an 
old-IDE legacy codepath:

[<c0371865>] error_code+0x65/0x6c
[<c0110155>] do_page_fault+0x0/0x1e0
[<c027dafc>] ide_complete_rq+0xf/0x3b
[<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
[<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
[<c027dcc2>] ide_intr+0x109/0x161
[<c0132298>] handle_IRQ_event+0x54/0xc7
[<c013354a>] handle_level_irq+0x4f/0x85
[<c0103df7>] handle_irq+0x17/0x20
[<c0103da5>] do_IRQ+0x2b/0x66
[<c0102be9>] common_interupt+0x29/0x30
[<c0480000>] cmd40x_init+0x2ac/0x38d
[<c0106db3>] default_idle+0x25/0x38
[<c01019be>] cpu_idle+0x19/0x2d
[<c0468907>] start_kernel+0x23f/0x242

report subject line is too unspecific, it should be changed to 
something like:

  legacy IDE cmd40x related bootup crash

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> Date		: 2009-05-12 7:59 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4

looks like wireless related - the dependency that connects the 
locks in a wrong way appears to be:

 -> #2 (cfg80211_mutex){+.+.+.}:
        [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
        [<ffffffff80271f38>] lock_acquire+0x98/0x140
        [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
        [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
        [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
        [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
        [<ffffffff8025dc3a>] kthread+0x5a/0xa0
        [<ffffffff8020d23a>] child_rip+0xa/0x20

(havent checked deeper)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> Subject		: possible circular locking dependency detected
> Submitter	: Miles Lane <miles.lane@gmail.com>
> Date		: 2009-05-04 16:56 (13 days old)

same as #13296 above. (The one above should be merged into this one 
i guess)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> Date		: 2009-04-15 12:43 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4

should be resolved via the lockdep space extension fix.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
> Date		: 2009-04-10 16:05 (37 days old)
> References	: http://lkml.org/lkml/2009/4/10/111
> 		  http://lkml.org/lkml/2009/4/25/83
> Handled-By	: Eric Dumazet <dada1@cosmosbay.com>

solved by:

 commit 942e4a2bd680c606af0211e64eb216be2e19bf61
 Author: Stephen Hemminger <shemminger@vyatta.com>
 Date:   Tue Apr 28 22:36:33 2009 -0700

    netfilter: revised locking for x_tables

commit log does not credit reporters and testers and does not 
mention bugzilla id.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> Subject		: Can't boot with nosmp
> Submitter	: Stephen Hemminger <shemminger@vyatta.com>
> Date		: 2009-04-15 4:18 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> Handled-By	: Dan Williams <dan.j.williams@intel.com>

I think this might be fixed by:

 d6de2c8: async: Fix module loading async-work regression

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

Oleg says in that thread that it's as-designed, and followup 
questions were not replied to (yet).

But ... a relevant seeming commit has been bisected to so this 
shouldnt be ignored that easily.

Andrew, you merged the commit that was bisected to:

  From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
  From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
  Date: Thu, 2 Apr 2009 16:58:08 -0700
  Subject: [PATCH] signals: protect cinit from blocked fatal signals

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> Subject		: Lockdep warining in inotify_dev_queue_event
> Submitter	: Sachin Sant <sachinp@in.ibm.com>
> Date		: 2009-04-05 12:37 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

should be fixed by:

381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

	Ingo

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> Submitter	: Jonathan Corbet <corbet@lwn.net>
> Date		: 2009-05-14 15:49 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4

Jonathan, there's a side-issue reported there, us running out of 
lockdep space. Could you try this commit from -tip:

d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS

(which i'll get to Linus in the next ~24 hours.) Maybe that allows 
lockdep to report the reason for the deadlock.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> Subject		: kernel crash with NULL pointer when boot
> Submitter	: Martin Bammer <mrb74@gmx.at>
> Date		: 2009-05-16 12:37 (1 days old)
> References	: http://lkml.org/lkml/2009/5/16/100

that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
xattr teardown.

There's been a good deal of reiserfs changes in this cycle - some 
touch the xattr code as well. Some of them fairly late in the cycle, 
in the last two weeks:

 earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
 2a32ceb: Fix races around the access to ->s_options
 677c9b2: reiserfs: remove privroot hiding in lookup
 b82bb72: reiserfs: dont associate security.* with xattr files
 ab17c4f: reiserfs: fixup xattr_root caching
 edcc37a: Always lookup priv_root on reiserfs mount and keep it
 5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len

Martin, you could try a blind revert of say ... ab17c4f, which looks 
the most suspect and which is also a rather large commit.

Or/and you could try a bisect - perhaps accelerated via:

   git bisect start fs/reiserfs/

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> Subject		: kernel panic -  not syncing : fatel exception in interupt
> Submitter	: rob <rob1@housetosell.net>
> Date		: 2009-05-12 19:34 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

tainted crash, but probably legit. It does show some badness in an 
old-IDE legacy codepath:

[<c0371865>] error_code+0x65/0x6c
[<c0110155>] do_page_fault+0x0/0x1e0
[<c027dafc>] ide_complete_rq+0xf/0x3b
[<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
[<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
[<c027dcc2>] ide_intr+0x109/0x161
[<c0132298>] handle_IRQ_event+0x54/0xc7
[<c013354a>] handle_level_irq+0x4f/0x85
[<c0103df7>] handle_irq+0x17/0x20
[<c0103da5>] do_IRQ+0x2b/0x66
[<c0102be9>] common_interupt+0x29/0x30
[<c0480000>] cmd40x_init+0x2ac/0x38d
[<c0106db3>] default_idle+0x25/0x38
[<c01019be>] cpu_idle+0x19/0x2d
[<c0468907>] start_kernel+0x23f/0x242

report subject line is too unspecific, it should be changed to 
something like:

  legacy IDE cmd40x related bootup crash

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> Date		: 2009-05-12 7:59 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4

looks like wireless related - the dependency that connects the 
locks in a wrong way appears to be:

 -> #2 (cfg80211_mutex){+.+.+.}:
        [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
        [<ffffffff80271f38>] lock_acquire+0x98/0x140
        [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
        [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
        [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
        [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
        [<ffffffff8025dc3a>] kthread+0x5a/0xa0
        [<ffffffff8020d23a>] child_rip+0xa/0x20

(havent checked deeper)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> Subject		: possible circular locking dependency detected
> Submitter	: Miles Lane <miles.lane@gmail.com>
> Date		: 2009-05-04 16:56 (13 days old)

same as #13296 above. (The one above should be merged into this one 
i guess)

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> Date		: 2009-04-15 12:43 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4

should be resolved via the lockdep space extension fix.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
> Date		: 2009-04-10 16:05 (37 days old)
> References	: http://lkml.org/lkml/2009/4/10/111
> 		  http://lkml.org/lkml/2009/4/25/83
> Handled-By	: Eric Dumazet <dada1@cosmosbay.com>

solved by:

 commit 942e4a2bd680c606af0211e64eb216be2e19bf61
 Author: Stephen Hemminger <shemminger@vyatta.com>
 Date:   Tue Apr 28 22:36:33 2009 -0700

    netfilter: revised locking for x_tables

commit log does not credit reporters and testers and does not 
mention bugzilla id.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> Subject		: Can't boot with nosmp
> Submitter	: Stephen Hemminger <shemminger@vyatta.com>
> Date		: 2009-04-15 4:18 (32 days old)
> References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> Handled-By	: Dan Williams <dan.j.williams@intel.com>

I think this might be fixed by:

 d6de2c8: async: Fix module loading async-work regression

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

Oleg says in that thread that it's as-designed, and followup 
questions were not replied to (yet).

But ... a relevant seeming commit has been bisected to so this 
shouldnt be ignored that easily.

Andrew, you merged the commit that was bisected to:

  From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
  From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
  Date: Thu, 2 Apr 2009 16:58:08 -0700
  Subject: [PATCH] signals: protect cinit from blocked fatal signals

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> Subject		: Lockdep warining in inotify_dev_queue_event
> Submitter	: Sachin Sant <sachinp@in.ibm.com>
> Date		: 2009-04-05 12:37 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4

should be fixed by:

381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

	Ingo

Re: [Bug #13068] Lockdep warining in inotify_dev_queue_event

[Sachin Sant]

Ingo Molnar wrote:
> i think this might be fixed by:
>
> 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive
>
> already in -rc6.
>   
Haven't seen this issue with rc6.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

Re: [Bug #13068] Lockdep warining in inotify_dev_queue_event

[Sachin Sant]

Ingo Molnar wrote:
> i think this might be fixed by:
>
> 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive
>
> already in -rc6.
>   
Haven't seen this issue with rc6.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

Re: [Bug #13068] Lockdep warining in inotify_dev_queue_event

[Rafael J. Wysocki]

On Sunday 17 May 2009, Sachin Sant wrote:
> Ingo Molnar wrote:
> > i think this might be fixed by:
> >
> > 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive
> >
> > already in -rc6.
> >   
> Haven't seen this issue with rc6.

Great, thanks.  Bug closed.

Best,
Rafael

Re: [Bug #13068] Lockdep warining in inotify_dev_queue_event

[Rafael J. Wysocki]

On Sunday 17 May 2009, Sachin Sant wrote:
> Ingo Molnar wrote:
> > i think this might be fixed by:
> >
> > 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive
> >
> > already in -rc6.
> >   
> Haven't seen this issue with rc6.

Great, thanks.  Bug closed.

Best,
Rafael

Re: [Bug #13118] iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

[Rafael J. Wysocki]

On Sunday 17 May 2009, Jeff Chua wrote:
> On Sun, May 17, 2009 at 3:20 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13118
> > Subject         : iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> > Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> > Date            : 2009-04-10 16:05 (37 days old)
> > References      : http://lkml.org/lkml/2009/4/10/111
> >                  http://lkml.org/lkml/2009/4/25/83
> > Handled-By      : Eric Dumazet <dada1@cosmosbay.com>
> 
> Fixed as of Apr 28.
> 
> commit 942e4a2bd680c606af0211e64eb216be2e19bf61
> Author: Stephen Hemminger <shemminger@vyatta.com>
> Date:   Tue Apr 28 22:36:33 2009 -0700
> 
>     netfilter: revised locking for x_tables

Thanks, closed.

Best,
Rafael

Re: [Bug #13118] iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49

[Rafael J. Wysocki]

On Sunday 17 May 2009, Jeff Chua wrote:
> On Sun, May 17, 2009 at 3:20 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> 
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13118
> > Subject         : iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> > Submitter       : Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date            : 2009-04-10 16:05 (37 days old)
> > References      : http://lkml.org/lkml/2009/4/10/111
> >                  http://lkml.org/lkml/2009/4/25/83
> > Handled-By      : Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
> 
> Fixed as of Apr 28.
> 
> commit 942e4a2bd680c606af0211e64eb216be2e19bf61
> Author: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
> Date:   Tue Apr 28 22:36:33 2009 -0700
> 
>     netfilter: revised locking for x_tables

Thanks, closed.

Best,
Rafael

Re: [Bug #13245] possible circular locking dependency detected

[Rafael J. Wysocki]

On Sunday 17 May 2009, Ming Lei wrote:
> I also can reproduce it on 2.6.30-rc5-next-20090515.
> 
> 2009/5/17 Rafael J. Wysocki <rjw@sisk.pl>:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13245
> > Subject         : possible circular locking dependency detected
> > Submitter       : Miles Lane <miles.lane@gmail.com>
> > Date            : 2009-05-04 16:56 (13 days old)

Thanks for the update.

Rafael

Re: [Bug #13245] possible circular locking dependency detected

[Rafael J. Wysocki]

On Sunday 17 May 2009, Ming Lei wrote:
> I also can reproduce it on 2.6.30-rc5-next-20090515.
> 
> 2009/5/17 Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13245
> > Subject         : possible circular locking dependency detected
> > Submitter       : Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date            : 2009-05-04 16:56 (13 days old)

Thanks for the update.

Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Sunday 17 May 2009, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> > Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> > Submitter	: Jonathan Corbet <corbet@lwn.net>
> > Date		: 2009-05-14 15:49 (3 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4
> 
> Jonathan, there's a side-issue reported there, us running out of 
> lockdep space. Could you try this commit from -tip:
> 
> d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS
> 
> (which i'll get to Linus in the next ~24 hours.) Maybe that allows 
> lockdep to report the reason for the deadlock.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> > Subject		: kernel crash with NULL pointer when boot
> > Submitter	: Martin Bammer <mrb74@gmx.at>
> > Date		: 2009-05-16 12:37 (1 days old)
> > References	: http://lkml.org/lkml/2009/5/16/100
> 
> that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
> xattr teardown.
> 
> There's been a good deal of reiserfs changes in this cycle - some 
> touch the xattr code as well. Some of them fairly late in the cycle, 
> in the last two weeks:
> 
>  earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
>  2a32ceb: Fix races around the access to ->s_options
>  677c9b2: reiserfs: remove privroot hiding in lookup
>  b82bb72: reiserfs: dont associate security.* with xattr files
>  ab17c4f: reiserfs: fixup xattr_root caching
>  edcc37a: Always lookup priv_root on reiserfs mount and keep it
>  5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len
> 
> Martin, you could try a blind revert of say ... ab17c4f, which looks 
> the most suspect and which is also a rather large commit.
> 
> Or/and you could try a bisect - perhaps accelerated via:
> 
>    git bisect start fs/reiserfs/

I think there's a fix already for this in the works, but it hasn't been merged
yet.  It looks like Jeff has just posted some reiserfs fixes. :-)

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1@housetosell.net>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> tainted crash, but probably legit. It does show some badness in an 
> old-IDE legacy codepath:
> 
> [<c0371865>] error_code+0x65/0x6c
> [<c0110155>] do_page_fault+0x0/0x1e0
> [<c027dafc>] ide_complete_rq+0xf/0x3b
> [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> [<c027dcc2>] ide_intr+0x109/0x161
> [<c0132298>] handle_IRQ_event+0x54/0xc7
> [<c013354a>] handle_level_irq+0x4f/0x85
> [<c0103df7>] handle_irq+0x17/0x20
> [<c0103da5>] do_IRQ+0x2b/0x66
> [<c0102be9>] common_interupt+0x29/0x30
> [<c0480000>] cmd40x_init+0x2ac/0x38d
> [<c0106db3>] default_idle+0x25/0x38
> [<c01019be>] cpu_idle+0x19/0x2d
> [<c0468907>] start_kernel+0x23f/0x242
> 
> report subject line is too unspecific, it should be changed to 
> something like:
> 
>   legacy IDE cmd40x related bootup crash
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> > Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> > Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> > Date		: 2009-05-12 7:59 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4
> 
> looks like wireless related - the dependency that connects the 
> locks in a wrong way appears to be:
> 
>  -> #2 (cfg80211_mutex){+.+.+.}:
>         [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
>         [<ffffffff80271f38>] lock_acquire+0x98/0x140
>         [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
>         [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
>         [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
>         [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
>         [<ffffffff8025dc3a>] kthread+0x5a/0xa0
>         [<ffffffff8020d23a>] child_rip+0xa/0x20
> 
> (havent checked deeper)
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> > Subject		: possible circular locking dependency detected
> > Submitter	: Miles Lane <miles.lane@gmail.com>
> > Date		: 2009-05-04 16:56 (13 days old)
> 
> same as #13296 above. (The one above should be merged into this one 
> i guess)

Yes, I've merged the two.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> > Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> > Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> > Date		: 2009-04-15 12:43 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4
> 
> should be resolved via the lockdep space extension fix.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> > Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> > Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
> > Date		: 2009-04-10 16:05 (37 days old)
> > References	: http://lkml.org/lkml/2009/4/10/111
> > 		  http://lkml.org/lkml/2009/4/25/83
> > Handled-By	: Eric Dumazet <dada1@cosmosbay.com>
> 
> solved by:
> 
>  commit 942e4a2bd680c606af0211e64eb216be2e19bf61
>  Author: Stephen Hemminger <shemminger@vyatta.com>
>  Date:   Tue Apr 28 22:36:33 2009 -0700
> 
>     netfilter: revised locking for x_tables

Already closed.

> commit log does not credit reporters and testers and does not 
> mention bugzilla id.

Sigh.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> > Subject		: Can't boot with nosmp
> > Submitter	: Stephen Hemminger <shemminger@vyatta.com>
> > Date		: 2009-04-15 4:18 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> > Handled-By	: Dan Williams <dan.j.williams@intel.com>
> 
> I think this might be fixed by:
> 
>  d6de2c8: async: Fix module loading async-work regression

That would be good to verify.  Stephen?

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> 
> Oleg says in that thread that it's as-designed, and followup 
> questions were not replied to (yet).
> 
> But ... a relevant seeming commit has been bisected to so this 
> shouldnt be ignored that easily.
> 
> Andrew, you merged the commit that was bisected to:
> 
>   From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
>   From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
>   Date: Thu, 2 Apr 2009 16:58:08 -0700
>   Subject: [PATCH] signals: protect cinit from blocked fatal signals
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> > Subject		: Lockdep warining in inotify_dev_queue_event
> > Submitter	: Sachin Sant <sachinp@in.ibm.com>
> > Date		: 2009-04-05 12:37 (42 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4
> 
> should be fixed by:
> 
> 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

Closed.

Thanks a lot,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Sunday 17 May 2009, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> > Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> > Submitter	: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>
> > Date		: 2009-05-14 15:49 (3 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4
> 
> Jonathan, there's a side-issue reported there, us running out of 
> lockdep space. Could you try this commit from -tip:
> 
> d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS
> 
> (which i'll get to Linus in the next ~24 hours.) Maybe that allows 
> lockdep to report the reason for the deadlock.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> > Subject		: kernel crash with NULL pointer when boot
> > Submitter	: Martin Bammer <mrb74-RbZlAiThDcE@public.gmane.org>
> > Date		: 2009-05-16 12:37 (1 days old)
> > References	: http://lkml.org/lkml/2009/5/16/100
> 
> that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
> xattr teardown.
> 
> There's been a good deal of reiserfs changes in this cycle - some 
> touch the xattr code as well. Some of them fairly late in the cycle, 
> in the last two weeks:
> 
>  earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
>  2a32ceb: Fix races around the access to ->s_options
>  677c9b2: reiserfs: remove privroot hiding in lookup
>  b82bb72: reiserfs: dont associate security.* with xattr files
>  ab17c4f: reiserfs: fixup xattr_root caching
>  edcc37a: Always lookup priv_root on reiserfs mount and keep it
>  5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len
> 
> Martin, you could try a blind revert of say ... ab17c4f, which looks 
> the most suspect and which is also a rather large commit.
> 
> Or/and you could try a bisect - perhaps accelerated via:
> 
>    git bisect start fs/reiserfs/

I think there's a fix already for this in the works, but it hasn't been merged
yet.  It looks like Jeff has just posted some reiserfs fixes. :-)

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> tainted crash, but probably legit. It does show some badness in an 
> old-IDE legacy codepath:
> 
> [<c0371865>] error_code+0x65/0x6c
> [<c0110155>] do_page_fault+0x0/0x1e0
> [<c027dafc>] ide_complete_rq+0xf/0x3b
> [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> [<c027dcc2>] ide_intr+0x109/0x161
> [<c0132298>] handle_IRQ_event+0x54/0xc7
> [<c013354a>] handle_level_irq+0x4f/0x85
> [<c0103df7>] handle_irq+0x17/0x20
> [<c0103da5>] do_IRQ+0x2b/0x66
> [<c0102be9>] common_interupt+0x29/0x30
> [<c0480000>] cmd40x_init+0x2ac/0x38d
> [<c0106db3>] default_idle+0x25/0x38
> [<c01019be>] cpu_idle+0x19/0x2d
> [<c0468907>] start_kernel+0x23f/0x242
> 
> report subject line is too unspecific, it should be changed to 
> something like:
> 
>   legacy IDE cmd40x related bootup crash
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> > Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> > Submitter	: Zdenek Kabelac <zdenek.kabelac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-05-12 7:59 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4
> 
> looks like wireless related - the dependency that connects the 
> locks in a wrong way appears to be:
> 
>  -> #2 (cfg80211_mutex){+.+.+.}:
>         [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
>         [<ffffffff80271f38>] lock_acquire+0x98/0x140
>         [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
>         [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
>         [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
>         [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
>         [<ffffffff8025dc3a>] kthread+0x5a/0xa0
>         [<ffffffff8020d23a>] child_rip+0xa/0x20
> 
> (havent checked deeper)
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> > Subject		: possible circular locking dependency detected
> > Submitter	: Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-05-04 16:56 (13 days old)
> 
> same as #13296 above. (The one above should be merged into this one 
> i guess)

Yes, I've merged the two.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> > Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> > Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-04-15 12:43 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4
> 
> should be resolved via the lockdep space extension fix.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> > Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> > Submitter	: Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-04-10 16:05 (37 days old)
> > References	: http://lkml.org/lkml/2009/4/10/111
> > 		  http://lkml.org/lkml/2009/4/25/83
> > Handled-By	: Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
> 
> solved by:
> 
>  commit 942e4a2bd680c606af0211e64eb216be2e19bf61
>  Author: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
>  Date:   Tue Apr 28 22:36:33 2009 -0700
> 
>     netfilter: revised locking for x_tables

Already closed.

> commit log does not credit reporters and testers and does not 
> mention bugzilla id.

Sigh.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> > Subject		: Can't boot with nosmp
> > Submitter	: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
> > Date		: 2009-04-15 4:18 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> > Handled-By	: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> I think this might be fixed by:
> 
>  d6de2c8: async: Fix module loading async-work regression

That would be good to verify.  Stephen?

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> 
> Oleg says in that thread that it's as-designed, and followup 
> questions were not replied to (yet).
> 
> But ... a relevant seeming commit has been bisected to so this 
> shouldnt be ignored that easily.
> 
> Andrew, you merged the commit that was bisected to:
> 
>   From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
>   From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
>   Date: Thu, 2 Apr 2009 16:58:08 -0700
>   Subject: [PATCH] signals: protect cinit from blocked fatal signals
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> > Subject		: Lockdep warining in inotify_dev_queue_event
> > Submitter	: Sachin Sant <sachinp-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
> > Date		: 2009-04-05 12:37 (42 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4
> 
> should be fixed by:
> 
> 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

Closed.

Thanks a lot,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Sunday 17 May 2009, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13325
> > Subject		: 2.6.30-rc kills my box hard - and lockdep chains
> > Submitter	: Jonathan Corbet <corbet@lwn.net>
> > Date		: 2009-05-14 15:49 (3 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124231630701394&w=4
> 
> Jonathan, there's a side-issue reported there, us running out of 
> lockdep space. Could you try this commit from -tip:
> 
> d80c19d: lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS
> 
> (which i'll get to Linus in the next ~24 hours.) Maybe that allows 
> lockdep to report the reason for the deadlock.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
> > Subject		: kernel crash with NULL pointer when boot
> > Submitter	: Martin Bammer <mrb74@gmx.at>
> > Date		: 2009-05-16 12:37 (1 days old)
> > References	: http://lkml.org/lkml/2009/5/16/100
> 
> that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
> xattr teardown.
> 
> There's been a good deal of reiserfs changes in this cycle - some 
> touch the xattr code as well. Some of them fairly late in the cycle, 
> in the last two weeks:
> 
>  earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
>  2a32ceb: Fix races around the access to ->s_options
>  677c9b2: reiserfs: remove privroot hiding in lookup
>  b82bb72: reiserfs: dont associate security.* with xattr files
>  ab17c4f: reiserfs: fixup xattr_root caching
>  edcc37a: Always lookup priv_root on reiserfs mount and keep it
>  5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len
> 
> Martin, you could try a blind revert of say ... ab17c4f, which looks 
> the most suspect and which is also a rather large commit.
> 
> Or/and you could try a bisect - perhaps accelerated via:
> 
>    git bisect start fs/reiserfs/

I think there's a fix already for this in the works, but it hasn't been merged
yet.  It looks like Jeff has just posted some reiserfs fixes. :-)

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1@housetosell.net>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> tainted crash, but probably legit. It does show some badness in an 
> old-IDE legacy codepath:
> 
> [<c0371865>] error_code+0x65/0x6c
> [<c0110155>] do_page_fault+0x0/0x1e0
> [<c027dafc>] ide_complete_rq+0xf/0x3b
> [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> [<c027dcc2>] ide_intr+0x109/0x161
> [<c0132298>] handle_IRQ_event+0x54/0xc7
> [<c013354a>] handle_level_irq+0x4f/0x85
> [<c0103df7>] handle_irq+0x17/0x20
> [<c0103da5>] do_IRQ+0x2b/0x66
> [<c0102be9>] common_interupt+0x29/0x30
> [<c0480000>] cmd40x_init+0x2ac/0x38d
> [<c0106db3>] default_idle+0x25/0x38
> [<c01019be>] cpu_idle+0x19/0x2d
> [<c0468907>] start_kernel+0x23f/0x242
> 
> report subject line is too unspecific, it should be changed to 
> something like:
> 
>   legacy IDE cmd40x related bootup crash
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13296
> > Subject		: Lockdep violation at cleanup_workqueue_thread during suspend
> > Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> > Date		: 2009-05-12 7:59 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124211522525625&w=4
> 
> looks like wireless related - the dependency that connects the 
> locks in a wrong way appears to be:
> 
>  -> #2 (cfg80211_mutex){+.+.+.}:
>         [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
>         [<ffffffff80271f38>] lock_acquire+0x98/0x140
>         [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
>         [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
>         [<ffffffffa007e66a>] reg_todo+0x19a/0x590 [cfg80211]
>         [<ffffffff80258f18>] worker_thread+0x1e8/0x3a0
>         [<ffffffff8025dc3a>] kthread+0x5a/0xa0
>         [<ffffffff8020d23a>] child_rip+0xa/0x20
> 
> (havent checked deeper)
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13245
> > Subject		: possible circular locking dependency detected
> > Submitter	: Miles Lane <miles.lane@gmail.com>
> > Date		: 2009-05-04 16:56 (13 days old)
> 
> same as #13296 above. (The one above should be merged into this one 
> i guess)

Yes, I've merged the two.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13126
> > Subject		: BUG: MAX_LOCKDEP_ENTRIES too low! when mounting rootfs
> > Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> > Date		: 2009-04-15 12:43 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123979949820538&w=4
> 
> should be resolved via the lockdep space extension fix.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13118
> > Subject		: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49
> > Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
> > Date		: 2009-04-10 16:05 (37 days old)
> > References	: http://lkml.org/lkml/2009/4/10/111
> > 		  http://lkml.org/lkml/2009/4/25/83
> > Handled-By	: Eric Dumazet <dada1@cosmosbay.com>
> 
> solved by:
> 
>  commit 942e4a2bd680c606af0211e64eb216be2e19bf61
>  Author: Stephen Hemminger <shemminger@vyatta.com>
>  Date:   Tue Apr 28 22:36:33 2009 -0700
> 
>     netfilter: revised locking for x_tables

Already closed.

> commit log does not credit reporters and testers and does not 
> mention bugzilla id.

Sigh.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13116
> > Subject		: Can't boot with nosmp
> > Submitter	: Stephen Hemminger <shemminger@vyatta.com>
> > Date		: 2009-04-15 4:18 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123976917817920&w=4
> > Handled-By	: Dan Williams <dan.j.williams@intel.com>
> 
> I think this might be fixed by:
> 
>  d6de2c8: async: Fix module loading async-work regression

That would be good to verify.  Stephen?

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> 
> Oleg says in that thread that it's as-designed, and followup 
> questions were not replied to (yet).
> 
> But ... a relevant seeming commit has been bisected to so this 
> shouldnt be ignored that easily.
> 
> Andrew, you merged the commit that was bisected to:
> 
>   From b3bfa0cba867f23365b81658b47efd906830879b Mon Sep 17 00:00:00 2001
>   From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
>   Date: Thu, 2 Apr 2009 16:58:08 -0700
>   Subject: [PATCH] signals: protect cinit from blocked fatal signals
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13068
> > Subject		: Lockdep warining in inotify_dev_queue_event
> > Submitter	: Sachin Sant <sachinp@in.ibm.com>
> > Date		: 2009-04-05 12:37 (42 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123893439229272&w=4
> 
> should be fixed by:
> 
> 381a80e: inotify: use GFP_NOFS in kernel_event() to work around a lockdep false-positive

Closed.

Thanks a lot,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Stefan Richter]

Rafael J. Wysocki wrote:
> On Sunday 17 May 2009, Ingo Molnar wrote:
>> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
>>> Subject		: kernel crash with NULL pointer when boot
>>> Submitter	: Martin Bammer <mrb74@gmx.at>
>>> Date		: 2009-05-16 12:37 (1 days old)
>>> References	: http://lkml.org/lkml/2009/5/16/100
>> that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
>> xattr teardown.
>>
>> There's been a good deal of reiserfs changes in this cycle - some 
>> touch the xattr code as well. Some of them fairly late in the cycle,

(Also, the bug is reportedly a post -rc5 regression.)

>> in the last two weeks:
>>
>>  earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
>>  2a32ceb: Fix races around the access to ->s_options
>>  677c9b2: reiserfs: remove privroot hiding in lookup
>>  b82bb72: reiserfs: dont associate security.* with xattr files
>>  ab17c4f: reiserfs: fixup xattr_root caching
>>  edcc37a: Always lookup priv_root on reiserfs mount and keep it
>>  5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len
>>
>> Martin, you could try a blind revert of say ... ab17c4f, which looks 
>> the most suspect and which is also a rather large commit.
>>
>> Or/and you could try a bisect - perhaps accelerated via:
>>
>>    git bisect start fs/reiserfs/
> 
> I think there's a fix already for this in the works, but it hasn't been merged
> yet.  It looks like Jeff has just posted some reiserfs fixes. :-)

I'd say Martin should try Jeff's pending patches before a revert or 
before starting a bisection.  Either apply them from 
http://lkml.org/lkml/2009/5/17/6, or pull from
  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git for-next
or wait for them to appear in Linus' tree...

I for one didn't test the post v2.6.30-rc5 changes to reiserfs, but I 
did try them _together_ with the four pending patches on a system with 
reiserfs root filesystem and extended attributes disabled in the config. 
Everything is fine here after almost a week uptime.
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Stefan Richter]

Rafael J. Wysocki wrote:
> On Sunday 17 May 2009, Ingo Molnar wrote:
>> * Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13321
>>> Subject		: kernel crash with NULL pointer when boot
>>> Submitter	: Martin Bammer <mrb74-RbZlAiThDcE@public.gmane.org>
>>> Date		: 2009-05-16 12:37 (1 days old)
>>> References	: http://lkml.org/lkml/2009/5/16/100
>> that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s 
>> xattr teardown.
>>
>> There's been a good deal of reiserfs changes in this cycle - some 
>> touch the xattr code as well. Some of them fairly late in the cycle,

(Also, the bug is reportedly a post -rc5 regression.)

>> in the last two weeks:
>>
>>  earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
>>  2a32ceb: Fix races around the access to ->s_options
>>  677c9b2: reiserfs: remove privroot hiding in lookup
>>  b82bb72: reiserfs: dont associate security.* with xattr files
>>  ab17c4f: reiserfs: fixup xattr_root caching
>>  edcc37a: Always lookup priv_root on reiserfs mount and keep it
>>  5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len
>>
>> Martin, you could try a blind revert of say ... ab17c4f, which looks 
>> the most suspect and which is also a rather large commit.
>>
>> Or/and you could try a bisect - perhaps accelerated via:
>>
>>    git bisect start fs/reiserfs/
> 
> I think there's a fix already for this in the works, but it hasn't been merged
> yet.  It looks like Jeff has just posted some reiserfs fixes. :-)

I'd say Martin should try Jeff's pending patches before a revert or 
before starting a bisection.  Either apply them from 
http://lkml.org/lkml/2009/5/17/6, or pull from
  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git for-next
or wait for them to appear in Linus' tree...

I for one didn't test the post v2.6.30-rc5 changes to reiserfs, but I 
did try them _together_ with the four pending patches on a system with 
reiserfs root filesystem and extended attributes disabled in the config. 
Everything is fine here after almost a week uptime.
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frederic Weisbecker]

On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1@housetosell.net>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> tainted crash, but probably legit. It does show some badness in an 
> old-IDE legacy codepath:
> 
> [<c0371865>] error_code+0x65/0x6c
> [<c0110155>] do_page_fault+0x0/0x1e0
> [<c027dafc>] ide_complete_rq+0xf/0x3b
> [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> [<c027dcc2>] ide_intr+0x109/0x161
> [<c0132298>] handle_IRQ_event+0x54/0xc7
> [<c013354a>] handle_level_irq+0x4f/0x85
> [<c0103df7>] handle_irq+0x17/0x20
> [<c0103da5>] do_IRQ+0x2b/0x66
> [<c0102be9>] common_interupt+0x29/0x30
> [<c0480000>] cmd40x_init+0x2ac/0x38d
> [<c0106db3>] default_idle+0x25/0x38
> [<c01019be>] cpu_idle+0x19/0x2d
> [<c0468907>] start_kernel+0x23f/0x242
> 
> report subject line is too unspecific, it should be changed to 
> something like:
> 
>   legacy IDE cmd40x related bootup crash


It seems the crash has been rewritten by hand. I don't see
any cmd40x_init(), I guess it's about cmd640 chipset, then
cmd640x_init()

I don't see very recent changes in drivers/ide/cmd640.c
But there are some in drivers/ide/ide-io.c and drivers/ide/ide-cd.c
for this cycle.

Especially commit a1f9a89c90b4ac143c5b6054c2a157572b272cd2 which
fixed in -rc2:

 Kernel Fault: Code=26 regs=8ed34c40 (Addr=00000024)
     IASQ: 00000000 00000000 IAOQ: 1034b5ac 1034b5b0
     IIR: 4ab30048    ISR: 00000000  IOR: 00000024
     CPU:        0   CR30: 8ed34000 CR31: ffff55ff
     ORIG_R28: 00000000
     IAOQ[0]: ide_complete_rq+0x2c/0x70
     IAOQ[1]: ide_complete_rq+0x30/0x70
     RP(r2): cdrom_newpc_intr+0x178/0x46c
    Backtrace:
     [<1035c608>] cdrom_newpc_intr+0x178/0x46c
     [<1034c494>] ide_intr+0x1b0/0x214
     [<1016d284>] handle_IRQ_event+0x70/0x150
     [<1016d4b0>] __do_IRQ+0x14c/0x1cc
     [<102f7864>] superio_interrupt+0x88/0xbc
     [<1016d284>] handle_IRQ_event+0x70/0x150
     [<1016d4b0>] __do_IRQ+0x14c/0x1cc
     [<10112efc>] do_cpu_irq_mask+0x9c/0xd0
     [<10116068>] intr_return+0x0/0x4

Looks very similar. But the crash reported in this ticket is for -rc4, which means the
issue was still there after this fix or it's another one.
Adding some more Cc's.

Frederic.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frederic Weisbecker]

On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> tainted crash, but probably legit. It does show some badness in an 
> old-IDE legacy codepath:
> 
> [<c0371865>] error_code+0x65/0x6c
> [<c0110155>] do_page_fault+0x0/0x1e0
> [<c027dafc>] ide_complete_rq+0xf/0x3b
> [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> [<c027dcc2>] ide_intr+0x109/0x161
> [<c0132298>] handle_IRQ_event+0x54/0xc7
> [<c013354a>] handle_level_irq+0x4f/0x85
> [<c0103df7>] handle_irq+0x17/0x20
> [<c0103da5>] do_IRQ+0x2b/0x66
> [<c0102be9>] common_interupt+0x29/0x30
> [<c0480000>] cmd40x_init+0x2ac/0x38d
> [<c0106db3>] default_idle+0x25/0x38
> [<c01019be>] cpu_idle+0x19/0x2d
> [<c0468907>] start_kernel+0x23f/0x242
> 
> report subject line is too unspecific, it should be changed to 
> something like:
> 
>   legacy IDE cmd40x related bootup crash


It seems the crash has been rewritten by hand. I don't see
any cmd40x_init(), I guess it's about cmd640 chipset, then
cmd640x_init()

I don't see very recent changes in drivers/ide/cmd640.c
But there are some in drivers/ide/ide-io.c and drivers/ide/ide-cd.c
for this cycle.

Especially commit a1f9a89c90b4ac143c5b6054c2a157572b272cd2 which
fixed in -rc2:

 Kernel Fault: Code=26 regs=8ed34c40 (Addr=00000024)
     IASQ: 00000000 00000000 IAOQ: 1034b5ac 1034b5b0
     IIR: 4ab30048    ISR: 00000000  IOR: 00000024
     CPU:        0   CR30: 8ed34000 CR31: ffff55ff
     ORIG_R28: 00000000
     IAOQ[0]: ide_complete_rq+0x2c/0x70
     IAOQ[1]: ide_complete_rq+0x30/0x70
     RP(r2): cdrom_newpc_intr+0x178/0x46c
    Backtrace:
     [<1035c608>] cdrom_newpc_intr+0x178/0x46c
     [<1034c494>] ide_intr+0x1b0/0x214
     [<1016d284>] handle_IRQ_event+0x70/0x150
     [<1016d4b0>] __do_IRQ+0x14c/0x1cc
     [<102f7864>] superio_interrupt+0x88/0xbc
     [<1016d284>] handle_IRQ_event+0x70/0x150
     [<1016d4b0>] __do_IRQ+0x14c/0x1cc
     [<10112efc>] do_cpu_irq_mask+0x9c/0xd0
     [<10116068>] intr_return+0x0/0x4

Looks very similar. But the crash reported in this ticket is for -rc4, which means the
issue was still there after this fix or it's another one.
Adding some more Cc's.

Frederic.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Richter wrote:
> Rafael J. Wysocki wrote:
>> On Sunday 17 May 2009, Ingo Molnar wrote:
>>> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13321
>>>> Subject        : kernel crash with NULL pointer when boot
>>>> Submitter    : Martin Bammer <mrb74@gmx.at>
>>>> Date        : 2009-05-16 12:37 (1 days old)
>>>> References    : http://lkml.org/lkml/2009/5/16/100
>>> that crash is in reiserfs_for_each_xattr(), during sys_unlink()'s
>>> xattr teardown.
>>>
>>> There's been a good deal of reiserfs changes in this cycle - some
>>> touch the xattr code as well. Some of them fairly late in the cycle,
> 
> (Also, the bug is reportedly a post -rc5 regression.)
> 
>>> in the last two weeks:
>>>
>>>  earth4:~/tip> gll v2.6.29..linus --since=two-weeks-ago fs/reiserfs/
>>>  2a32ceb: Fix races around the access to ->s_options
>>>  677c9b2: reiserfs: remove privroot hiding in lookup
>>>  b82bb72: reiserfs: dont associate security.* with xattr files
>>>  ab17c4f: reiserfs: fixup xattr_root caching
>>>  edcc37a: Always lookup priv_root on reiserfs mount and keep it
>>>  5a6059c: reiserfs: Expand i_mutex to enclose lookup_one_len
>>>
>>> Martin, you could try a blind revert of say ... ab17c4f, which looks
>>> the most suspect and which is also a rather large commit.
>>>
>>> Or/and you could try a bisect - perhaps accelerated via:
>>>
>>>    git bisect start fs/reiserfs/
>>
>> I think there's a fix already for this in the works, but it hasn't
>> been merged
>> yet.  It looks like Jeff has just posted some reiserfs fixes. :-)
> 
> I'd say Martin should try Jeff's pending patches before a revert or
> before starting a bisection.  Either apply them from
> http://lkml.org/lkml/2009/5/17/6, or pull from
>  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git for-next
> or wait for them to appear in Linus' tree...
> 
> I for one didn't test the post v2.6.30-rc5 changes to reiserfs, but I
> did try them _together_ with the four pending patches on a system with
> reiserfs root filesystem and extended attributes disabled in the config.
> Everything is fine here after almost a week uptime.

Yes, this bug is known and is fixed with "[patch 2/4] [PATCH] reiserfs:
deal with NULL xattr root w/ xattrs disabled"

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkoQGEIACgkQLPWxlyuTD7K8kwCfUEq36jJvY+FzzuvWbAyOYX+r
BPwAniRe6a7Cj8n5+vC2Zmwfp1hRRUb1
=fh19
-----END PGP SIGNATURE-----

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Greg KH]

On Sat, May 16, 2009 at 07:13:59PM -0700, Linus Torvalds wrote:
> 
> 
> On Sun, 17 May 2009, Kay Sievers wrote:
> > 
> > This makes the oops in the driver-core, caused by the rtc driver
> > unregister, go away. The original issue is also fixed in the rtc driver
> > itself.
> 
> I don't think this is sufficient.
> 
> > --- a/drivers/base/driver.c
> > +++ b/drivers/base/driver.c
> > @@ -257,6 +257,8 @@ EXPORT_SYMBOL_GPL(driver_register);
> >   */
> >  void driver_unregister(struct device_driver *drv)
> >  {
> > +	if (!drv || !drv->p)
> > +		return;
> >  	driver_remove_groups(drv, drv->groups);
> >  	bus_remove_driver(drv);
> >  }
> 
> Ok, fine so far, but look at "driver_register()".
> 
> It will set drv->p, but then not unset it if it fails! (For a certain 
> class of failures)
> 
> So for a certain failure pattern, drv->p will point to some stale value. 
> Should we not clear drv->p in the "out_unregister" patch?
> 
> To confuse the thing more, there are actually "half-way failures" that 
> _succeed_ in driver registration, but then return an error code. See that 
> whole
> 
> 
> 	kobject_uevent(&priv->kobj, KOBJ_ADD);
> 	return error;
> 
> case in the "success" path driver_register(). We may return an error 
> despite the fact that we actually attached the driver to bus, but 
> "add_bind_files()" failed. A caller would be understandable very unhappy.
> 
> So I suspect we should do something like the appended (in addition to your 
> patch). Comments?

That looks good.  I'll add the WARN_ON that Ingo pointed out, and merge
this with Kay's patch.  Give me a few hours to wake up...

thanks,

greg k-h

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Borislav Petkov]

Hi,

On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > Submitter	: rob <rob1@housetosell.net>
> > > Date		: 2009-05-12 19:34 (5 days old)
> > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > 
> > tainted crash, but probably legit. It does show some badness in an 
> > old-IDE legacy codepath:
> > 
> > [<c0371865>] error_code+0x65/0x6c
> > [<c0110155>] do_page_fault+0x0/0x1e0
> > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > [<c027dcc2>] ide_intr+0x109/0x161
> > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > [<c013354a>] handle_level_irq+0x4f/0x85
> > [<c0103df7>] handle_irq+0x17/0x20
> > [<c0103da5>] do_IRQ+0x2b/0x66
> > [<c0102be9>] common_interupt+0x29/0x30
> > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > [<c0106db3>] default_idle+0x25/0x38
> > [<c01019be>] cpu_idle+0x19/0x2d
> > [<c0468907>] start_kernel+0x23f/0x242
> > 
> > report subject line is too unspecific, it should be changed to 
> > something like:
> > 
> >   legacy IDE cmd40x related bootup crash
> 
> 
> It seems the crash has been rewritten by hand. I don't see
> any cmd40x_init(), I guess it's about cmd640 chipset, then
> cmd640x_init()
> 
> I don't see very recent changes in drivers/ide/cmd640.c
> But there are some in drivers/ide/ide-io.c and drivers/ide/ide-cd.c
> for this cycle.
> 
> Especially commit a1f9a89c90b4ac143c5b6054c2a157572b272cd2 which
> fixed in -rc2:
> 
>  Kernel Fault: Code=26 regs=8ed34c40 (Addr=00000024)
>      IASQ: 00000000 00000000 IAOQ: 1034b5ac 1034b5b0
>      IIR: 4ab30048    ISR: 00000000  IOR: 00000024
>      CPU:        0   CR30: 8ed34000 CR31: ffff55ff
>      ORIG_R28: 00000000
>      IAOQ[0]: ide_complete_rq+0x2c/0x70
>      IAOQ[1]: ide_complete_rq+0x30/0x70
>      RP(r2): cdrom_newpc_intr+0x178/0x46c
>     Backtrace:
>      [<1035c608>] cdrom_newpc_intr+0x178/0x46c
>      [<1034c494>] ide_intr+0x1b0/0x214
>      [<1016d284>] handle_IRQ_event+0x70/0x150
>      [<1016d4b0>] __do_IRQ+0x14c/0x1cc
>      [<102f7864>] superio_interrupt+0x88/0xbc
>      [<1016d284>] handle_IRQ_event+0x70/0x150
>      [<1016d4b0>] __do_IRQ+0x14c/0x1cc
>      [<10112efc>] do_cpu_irq_mask+0x9c/0xd0
>      [<10116068>] intr_return+0x0/0x4
> 
> Looks very similar. But the crash reported in this ticket is for -rc4, which means the
> issue was still there after this fix or it's another one.
> Adding some more Cc's.

yep, I'm already looking into it.

-- 
Regards/Gruss,
    Boris.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Borislav Petkov]

Hi,

On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
> > > Date		: 2009-05-12 19:34 (5 days old)
> > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > 
> > tainted crash, but probably legit. It does show some badness in an 
> > old-IDE legacy codepath:
> > 
> > [<c0371865>] error_code+0x65/0x6c
> > [<c0110155>] do_page_fault+0x0/0x1e0
> > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > [<c027dcc2>] ide_intr+0x109/0x161
> > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > [<c013354a>] handle_level_irq+0x4f/0x85
> > [<c0103df7>] handle_irq+0x17/0x20
> > [<c0103da5>] do_IRQ+0x2b/0x66
> > [<c0102be9>] common_interupt+0x29/0x30
> > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > [<c0106db3>] default_idle+0x25/0x38
> > [<c01019be>] cpu_idle+0x19/0x2d
> > [<c0468907>] start_kernel+0x23f/0x242
> > 
> > report subject line is too unspecific, it should be changed to 
> > something like:
> > 
> >   legacy IDE cmd40x related bootup crash
> 
> 
> It seems the crash has been rewritten by hand. I don't see
> any cmd40x_init(), I guess it's about cmd640 chipset, then
> cmd640x_init()
> 
> I don't see very recent changes in drivers/ide/cmd640.c
> But there are some in drivers/ide/ide-io.c and drivers/ide/ide-cd.c
> for this cycle.
> 
> Especially commit a1f9a89c90b4ac143c5b6054c2a157572b272cd2 which
> fixed in -rc2:
> 
>  Kernel Fault: Code=26 regs=8ed34c40 (Addr=00000024)
>      IASQ: 00000000 00000000 IAOQ: 1034b5ac 1034b5b0
>      IIR: 4ab30048    ISR: 00000000  IOR: 00000024
>      CPU:        0   CR30: 8ed34000 CR31: ffff55ff
>      ORIG_R28: 00000000
>      IAOQ[0]: ide_complete_rq+0x2c/0x70
>      IAOQ[1]: ide_complete_rq+0x30/0x70
>      RP(r2): cdrom_newpc_intr+0x178/0x46c
>     Backtrace:
>      [<1035c608>] cdrom_newpc_intr+0x178/0x46c
>      [<1034c494>] ide_intr+0x1b0/0x214
>      [<1016d284>] handle_IRQ_event+0x70/0x150
>      [<1016d4b0>] __do_IRQ+0x14c/0x1cc
>      [<102f7864>] superio_interrupt+0x88/0xbc
>      [<1016d284>] handle_IRQ_event+0x70/0x150
>      [<1016d4b0>] __do_IRQ+0x14c/0x1cc
>      [<10112efc>] do_cpu_irq_mask+0x9c/0xd0
>      [<10116068>] intr_return+0x0/0x4
> 
> Looks very similar. But the crash reported in this ticket is for -rc4, which means the
> issue was still there after this fix or it's another one.
> Adding some more Cc's.

yep, I'm already looking into it.

-- 
Regards/Gruss,
    Boris.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Alex Bennee]

2009/5/16 Rafael J. Wysocki <rjw@sisk.pl>:
> This message contains a list of some regressions from 2.6.29, for which there
> are no fixes in the mainline I know of.  If any of them have been fixed already,
> please let me know.
>
> If you know of any other unresolved regressions from 2.6.29, please let me know
> either and I'll add them to the list.  Also, please let me know if any of the
> entries below are invalid.
>
> Each entry from the list will be sent additionally in an automatic reply to
> this message with CCs to the people involved in reporting and handling the
> issue.

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13171
> Subject         : 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
> Submitter       : Alex Bennee <kernel-hacker@bennee.com>
> Date            : 2009-04-19 6:27 (28 days old)
> References      : http://marc.info/?l=linux-kernel&m=124022460014812&w=4

All the main details on this are on the freedesktop bugzilla[1]. I can
confirm it's still a problem and I've been tracking the intel-next
tree for testing.

Fundamentally the problem is that X can't allocate any memory when KMS
is enabled on my chipset. Without knowing how memory should be
allocated from the kernel by the X driver I haven't been able to look
into it deeper. I've had some feedback from the intel guys but nothing
recently.

As always I stand ready to run tests and/or provide additional
diagnostics if required.


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

-- 
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Alex Bennee]

2009/5/16 Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>:
> This message contains a list of some regressions from 2.6.29, for which there
> are no fixes in the mainline I know of.  If any of them have been fixed already,
> please let me know.
>
> If you know of any other unresolved regressions from 2.6.29, please let me know
> either and I'll add them to the list.  Also, please let me know if any of the
> entries below are invalid.
>
> Each entry from the list will be sent additionally in an automatic reply to
> this message with CCs to the people involved in reporting and handling the
> issue.

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13171
> Subject         : 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
> Submitter       : Alex Bennee <kernel-hacker-jriKODhXDevQT0dZR+AlfA@public.gmane.org>
> Date            : 2009-04-19 6:27 (28 days old)
> References      : http://marc.info/?l=linux-kernel&m=124022460014812&w=4

All the main details on this are on the freedesktop bugzilla[1]. I can
confirm it's still a problem and I've been tracking the intel-next
tree for testing.

Fundamentally the problem is that X can't allocate any memory when KMS
is enabled on my chipset. Without knowing how memory should be
allocated from the kernel by the X driver I haven't been able to look
into it deeper. I've had some feedback from the intel guys but nothing
recently.

As always I stand ready to run tests and/or provide additional
diagnostics if required.


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

-- 
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
>
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

I think we have to revert that thing. I haven't heard of any fixes to that 
commit.

		Linus

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
>
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

I think we have to revert that thing. I haven't heard of any fixes to that 
commit.

		Linus

Re: [Bug #13122] reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
> Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
> Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> Date		: 2009-04-16 19:23 (31 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
> References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
> Handled-By	: Jeff Mahoney <jeffm@suse.com>
> Patch		: http://lkml.org/lkml/2009/5/10/91

The fix should now be merged as b83674c0da6558e357c6b482ccf299eeea77d8ef 
("reiserfs: fixup perms when xattrs are disabled")

		Linus

Re: [Bug #13122] reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
> Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
> Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-04-16 19:23 (31 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
> References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
> Handled-By	: Jeff Mahoney <jeffm-IBi9RG/b67k@public.gmane.org>
> Patch		: http://lkml.org/lkml/2009/5/10/91

The fix should now be merged as b83674c0da6558e357c6b482ccf299eeea77d8ef 
("reiserfs: fixup perms when xattrs are disabled")

		Linus

Re: [Bug #13122] reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)

[Rafael J. Wysocki]

On Sunday 17 May 2009, Linus Torvalds wrote:
> 
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
> > Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
> > Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
> > Date		: 2009-04-16 19:23 (31 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
> > References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
> > Handled-By	: Jeff Mahoney <jeffm@suse.com>
> > Patch		: http://lkml.org/lkml/2009/5/10/91
> 
> The fix should now be merged as b83674c0da6558e357c6b482ccf299eeea77d8ef 
> ("reiserfs: fixup perms when xattrs are disabled")

Thanks, closed.

Rafael

Re: [Bug #13122] reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)

[Rafael J. Wysocki]

On Sunday 17 May 2009, Linus Torvalds wrote:
> 
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13122
> > Subject		: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
> > Submitter	: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-04-16 19:23 (31 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d984561b326cd0fe0d1183d11b9b4fa1d011d21d
> > References	: http://marc.info/?l=linux-kernel&m=123990989515105&w=4
> > Handled-By	: Jeff Mahoney <jeffm-IBi9RG/b67k@public.gmane.org>
> > Patch		: http://lkml.org/lkml/2009/5/10/91
> 
> The fix should now be merged as b83674c0da6558e357c6b482ccf299eeea77d8ef 
> ("reiserfs: fixup perms when xattrs are disabled")

Thanks, closed.

Rafael

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Larry Finger]

Andrew Morton wrote:
> 
> Well..  order-1 GFP_ATOMIC allocations are unreliable.  The networking
> code should hanlde the situation and recover.  I assume that is
> happening in this case?

Yes, the driver has recovered in all cases so far.

> Perhaps we did something in that code after 2.6.29 which increased the
> frequency of the order-1 allocation attempts?  Maybe earlier kernels
> used order-0 all the time?  Those are much more reliable.

I think something happened to change the allocation as I never saw these O(1)
failures before with these particular drivers. I put in a few test printk's and
the buffers were 700-800 bytes long, and I would not expect them to require more
than an O(0) allocation.

I pushed 2.6.30-rc6 hard for ~12 hours without any recurrence of the problem.
Given the relative infrequency of the error, this certainly does not indicate a
fix in recent code. I will be trying to force it again.

Larry

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Larry Finger]

Andrew Morton wrote:
> 
> Well..  order-1 GFP_ATOMIC allocations are unreliable.  The networking
> code should hanlde the situation and recover.  I assume that is
> happening in this case?

Yes, the driver has recovered in all cases so far.

> Perhaps we did something in that code after 2.6.29 which increased the
> frequency of the order-1 allocation attempts?  Maybe earlier kernels
> used order-0 all the time?  Those are much more reliable.

I think something happened to change the allocation as I never saw these O(1)
failures before with these particular drivers. I put in a few test printk's and
the buffers were 700-800 bytes long, and I would not expect them to require more
than an O(0) allocation.

I pushed 2.6.30-rc6 hard for ~12 hours without any recurrence of the problem.
Given the relative infrequency of the error, this certainly does not indicate a
fix in recent code. I will be trying to force it again.

Larry

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

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Greg KH]

On Sat, May 16, 2009 at 07:13:59PM -0700, Linus Torvalds wrote:
> On Sun, 17 May 2009, Kay Sievers wrote:
> > 
> > This makes the oops in the driver-core, caused by the rtc driver
> > unregister, go away. The original issue is also fixed in the rtc driver
> > itself.
> 
> I don't think this is sufficient.
> 
> > --- a/drivers/base/driver.c
> > +++ b/drivers/base/driver.c
> > @@ -257,6 +257,8 @@ EXPORT_SYMBOL_GPL(driver_register);
> >   */
> >  void driver_unregister(struct device_driver *drv)
> >  {
> > +	if (!drv || !drv->p)
> > +		return;
> >  	driver_remove_groups(drv, drv->groups);
> >  	bus_remove_driver(drv);
> >  }
> 
> Ok, fine so far, but look at "driver_register()".
> 
> It will set drv->p, but then not unset it if it fails! (For a certain 
> class of failures)
> 
> So for a certain failure pattern, drv->p will point to some stale value. 
> Should we not clear drv->p in the "out_unregister" patch?
> 
> To confuse the thing more, there are actually "half-way failures" that 
> _succeed_ in driver registration, but then return an error code. See that 
> whole
> 
> 
> 	kobject_uevent(&priv->kobj, KOBJ_ADD);
> 	return error;
> 
> case in the "success" path driver_register(). We may return an error 
> despite the fact that we actually attached the driver to bus, but 
> "add_bind_files()" failed. A caller would be understandable very unhappy.
> 
> So I suspect we should do something like the appended (in addition to your 
> patch). Comments?

Yes, that's needed.  We also don't clean up properly when we do the same
thing for devices (error in the initialization of them).

So, here's a patch that combines everyone's intentions in this thread.
Any objections to it?

thanks,

greg k-h

------------------------
From: Kay Sievers <kay.sievers@vrfy.org>
Subject: Driver Core: do not oops when driver_unregister() is called for unregistered drivers

We also fix a problem with cleaning up properly when initializing
drivers and devices, so checks like this will work successfully.

Portions of the patch by Linus and Greg and Ingo.

Reported-by: Ozan Çağlayan <ozan@pardus.org.tr>
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

diff --git a/drivers/base/bus.c b/drivers/base/bus.c
index dc030f1..c659961 100644
--- a/drivers/base/bus.c
+++ b/drivers/base/bus.c
@@ -700,8 +700,10 @@ int bus_add_driver(struct device_driver *drv)
 	}
 
 	kobject_uevent(&priv->kobj, KOBJ_ADD);
-	return error;
+	return 0;
 out_unregister:
+	kfree(drv->p);
+	drv->p = NULL;
 	kobject_put(&priv->kobj);
 out_put_bus:
 	bus_put(bus);
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 4aa527b..1977d4b 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -879,7 +879,7 @@ int device_add(struct device *dev)
 	}
 
 	if (!dev_name(dev))
-		goto done;
+		goto name_error;
 
 	pr_debug("device: '%s': %s\n", dev_name(dev), __func__);
 
@@ -978,6 +978,9 @@ done:
 	cleanup_device_parent(dev);
 	if (parent)
 		put_device(parent);
+name_error:
+	kfree(dev->p);
+	dev->p = NULL;
 	goto done;
 }
 
diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index c51f11b..8ae0f63 100644
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -257,6 +257,10 @@ EXPORT_SYMBOL_GPL(driver_register);
  */
 void driver_unregister(struct device_driver *drv)
 {
+	if (!drv || !drv->p) {
+		WARN(1, "Unexpected driver unregister!\n");
+		return;
+	}
 	driver_remove_groups(drv, drv->groups);
 	bus_remove_driver(drv);
 }

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Pekka Enberg]

Hi Andrew,

On Sat, 16 May 2009 21:20:45 +0200 (CEST) "Rafael J. Wysocki"
<rjw@sisk.pl> wrote:
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.29.  Please verify if it still should be listed and let me know
>> (either way).
>>
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13319
>> Subject               : Page allocation failures with b43 and p54usb
>> Submitter     : Larry Finger <Larry.Finger@lwfinger.net>
>> Date          : 2009-04-29 21:01 (18 days old)
>> References    : http://marc.info/?l=linux-kernel&m=124103897101088&w=4
>> Handled-By    : Johannes Berg <johannes@sipsolutions.net>

On Sun, May 17, 2009 at 2:36 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> Well..  order-1 GFP_ATOMIC allocations are unreliable.  The networking
> code should hanlde the situation and recover.  I assume that is
> happening in this case?
>
> Perhaps we did something in that code after 2.6.29 which increased the
> frequency of the order-1 allocation attempts?  Maybe earlier kernels
> used order-0 all the time?  Those are much more reliable.

I wonder if this is related:

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

Both point to post 2.6.29... Hmm.

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Pekka Enberg]

Hi Andrew,

On Sat, 16 May 2009 21:20:45 +0200 (CEST) "Rafael J. Wysocki"
<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.29.  Please verify if it still should be listed and let me know
>> (either way).
>>
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13319
>> Subject               : Page allocation failures with b43 and p54usb
>> Submitter     : Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
>> Date          : 2009-04-29 21:01 (18 days old)
>> References    : http://marc.info/?l=linux-kernel&m=124103897101088&w=4
>> Handled-By    : Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

On Sun, May 17, 2009 at 2:36 AM, Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:
> Well..  order-1 GFP_ATOMIC allocations are unreliable.  The networking
> code should hanlde the situation and recover.  I assume that is
> happening in this case?
>
> Perhaps we did something in that code after 2.6.29 which increased the
> frequency of the order-1 allocation attempts?  Maybe earlier kernels
> used order-0 all the time?  Those are much more reliable.

I wonder if this is related:

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

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

Re: [Bug #13177] 2.6.30-rc2-git7 build problem

[Martin Knoblauch]

----- Original Message ----
> From: Rafael J. Wysocki <rjw@sisk.pl>
> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Cc: Kernel Testers List <kernel-testers@vger.kernel.org>; Martin Knoblauch <spamtrap@knobisoft.de>
> Sent: Saturday, May 16, 2009 9:20:40 PM
> Subject: [Bug #13177] 2.6.30-rc2-git7 build problem
> 
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13177
> Subject        : 2.6.30-rc2-git7 build problem
> Submitter    : Martin Knoblauch 
> Date        : 2009-04-21 13:39 (26 days old)
> References    : http://marc.info/?l=linux-kernel&m=124032163602132&w=4
>           http://lkml.org/lkml/2009/4/27/56

 Still a problem in 2.6.30-rc6-git3. Adding maintainer

BUILD   arch/x86/boot/bzImage
Root device is (104, 3)
Setup is 12664 bytes (padded to 12800 bytes).
System is 2648 kB
CRC 91a1a400
Kernel: arch/x86/boot/bzImage is ready  (#2)
  Building modules, stage 2.
  MODPOST 471 modules
WARNING: drivers/gpu/drm/i915/i915.o(.text+0x1313e): Section mismatch in reference from the function intel_lvds_init() to the variable .init.data:intel_no_lvds
The function intel_lvds_init() references
the variable __initdata intel_no_lvds.
This is often because intel_lvds_init lacks a __initdata
annotation or the annotation of intel_no_lvds is wrong.

ERROR: ".L192" [drivers/usb/serial/kl5kusb105.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

Cheers
Martin

Re: [Bug #13177] 2.6.30-rc2-git7 build problem

[Martin Knoblauch]

----- Original Message ----
> From: Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
> To: Linux Kernel Mailing List <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
> Cc: Kernel Testers List <kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>; Martin Knoblauch <spamtrap-Ys4E+72pFW0hFhg+JK9F0w@public.gmane.org>
> Sent: Saturday, May 16, 2009 9:20:40 PM
> Subject: [Bug #13177] 2.6.30-rc2-git7 build problem
> 
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13177
> Subject        : 2.6.30-rc2-git7 build problem
> Submitter    : Martin Knoblauch 
> Date        : 2009-04-21 13:39 (26 days old)
> References    : http://marc.info/?l=linux-kernel&m=124032163602132&w=4
>           http://lkml.org/lkml/2009/4/27/56

 Still a problem in 2.6.30-rc6-git3. Adding maintainer

BUILD   arch/x86/boot/bzImage
Root device is (104, 3)
Setup is 12664 bytes (padded to 12800 bytes).
System is 2648 kB
CRC 91a1a400
Kernel: arch/x86/boot/bzImage is ready  (#2)
  Building modules, stage 2.
  MODPOST 471 modules
WARNING: drivers/gpu/drm/i915/i915.o(.text+0x1313e): Section mismatch in reference from the function intel_lvds_init() to the variable .init.data:intel_no_lvds
The function intel_lvds_init() references
the variable __initdata intel_no_lvds.
This is often because intel_lvds_init lacks a __initdata
annotation or the annotation of intel_no_lvds is wrong.

ERROR: ".L192" [drivers/usb/serial/kl5kusb105.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

Cheers
Martin

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Oleg Nesterov]

Sorry for delay, I had a vacation.

On 05/17, Linus Torvalds wrote:
>
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> >
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
>
> I think we have to revert that thing. I haven't heard of any fixes to that
> commit.

I thought this was already resolved.

And I don't think the kernel is buggy, this is expected behaviour. With
this commit (actually, there were several patches) /sbin/init respects
SIGSTOP if the caller has rights to send it, this change is intentional.
I'd even say this is fix.

Note that even root can't stop init, SIGSTOP should be sent from the
parent namespace, or from ptracer. And ptracer could obviously ptrace_stop()
init even before this patch.


But, Kumar, could you please provide more info? I downloaded
ltp-full-20081130.tgz, and I see that ptrace03.c does:

                        /* since Linux 2.6.26, it's allowed to trace init,
                           so just skip this test case */
                        if (i == 0 && tst_kvercmp(2,6,25) > 0) {
                                tst_resm(TCONF,
                                         "this kernel allows to trace init");
                                continue;
                        }

So, could you explain which test traces init?

Oleg.

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Oleg Nesterov]

Sorry for delay, I had a vacation.

On 05/17, Linus Torvalds wrote:
>
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> >
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
>
> I think we have to revert that thing. I haven't heard of any fixes to that
> commit.

I thought this was already resolved.

And I don't think the kernel is buggy, this is expected behaviour. With
this commit (actually, there were several patches) /sbin/init respects
SIGSTOP if the caller has rights to send it, this change is intentional.
I'd even say this is fix.

Note that even root can't stop init, SIGSTOP should be sent from the
parent namespace, or from ptracer. And ptracer could obviously ptrace_stop()
init even before this patch.


But, Kumar, could you please provide more info? I downloaded
ltp-full-20081130.tgz, and I see that ptrace03.c does:

                        /* since Linux 2.6.26, it's allowed to trace init,
                           so just skip this test case */
                        if (i == 0 && tst_kvercmp(2,6,25) > 0) {
                                tst_resm(TCONF,
                                         "this kernel allows to trace init");
                                continue;
                        }

So, could you explain which test traces init?

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/17, Ingo Molnar wrote:
>
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
>
> Oleg says in that thread that it's as-designed, and followup
> questions were not replied to (yet).

Yes, I think this is false alarm. Perhaps I missed something, and
I am waiting for more info from Kumar, but it looks like ltp was
already changed to skip the "{ PTRACE_ATTACH, 1, EPERM }" test
on kernels after 2.6.25

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/17, Ingo Molnar wrote:
>
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
>
> Oleg says in that thread that it's as-designed, and followup
> questions were not replied to (yet).

Yes, I think this is false alarm. Perhaps I missed something, and
I am waiting for more info from Kumar, but it looks like ltp was
already changed to skip the "{ PTRACE_ATTACH, 1, EPERM }" test
on kernels after 2.6.25

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Oleg Nesterov <oleg@redhat.com> wrote:

> On 05/17, Ingo Molnar wrote:
> >
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > > Date		: 2009-04-09 15:43 (38 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > > 		  http://lkml.org/lkml/2009/4/10/193
> > > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> >
> > Oleg says in that thread that it's as-designed, and followup
> > questions were not replied to (yet).
> 
> Yes, I think this is false alarm. Perhaps I missed something, and 
> I am waiting for more info from Kumar, but it looks like ltp was 
> already changed to skip the "{ PTRACE_ATTACH, 1, EPERM }" test on 
> kernels after 2.6.25

Btw., why did the patch (and the revert) make any difference to the 
test? Timing differences look improbable.

	Ingo

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Ingo Molnar]

* Oleg Nesterov <oleg@redhat.com> wrote:

> On 05/17, Ingo Molnar wrote:
> >
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > > Date		: 2009-04-09 15:43 (38 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > > 		  http://lkml.org/lkml/2009/4/10/193
> > > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> >
> > Oleg says in that thread that it's as-designed, and followup
> > questions were not replied to (yet).
> 
> Yes, I think this is false alarm. Perhaps I missed something, and 
> I am waiting for more info from Kumar, but it looks like ltp was 
> already changed to skip the "{ PTRACE_ATTACH, 1, EPERM }" test on 
> kernels after 2.6.25

Btw., why did the patch (and the revert) make any difference to the 
test? Timing differences look improbable.

	Ingo

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/18, Ingo Molnar wrote:
>
> * Oleg Nesterov <oleg@redhat.com> wrote:
>
> > On 05/17, Ingo Molnar wrote:
> > >
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > > > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > > > Date		: 2009-04-09 15:43 (38 days old)
> > > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > > > 		  http://lkml.org/lkml/2009/4/10/193
> > > > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> > >
> > > Oleg says in that thread that it's as-designed, and followup
> > > questions were not replied to (yet).
> >
> > Yes, I think this is false alarm. Perhaps I missed something, and
> > I am waiting for more info from Kumar, but it looks like ltp was
> > already changed to skip the "{ PTRACE_ATTACH, 1, EPERM }" test on
> > kernels after 2.6.25
>
> Btw., why did the patch (and the revert) make any difference to the
> test? Timing differences look improbable.

Because before this series /sbin/init always ignored SIGSTOP. Now,
ptracer does PTRACE_ATTACH and exits without clearing the pending
SIGSTOP. init dequeues this signal and becomes TASK_STOPPED.

Consider:

	$ sleep 1000 &
	[1] 875

	$ grep State: /proc/`pidof sleep`/status
	State:  S (sleeping)

	$ perl -e 'syscall 101, 16, 0+shift, 0,0' `pidof sleep`    # just PTRACE_ATTACH + exit

	[1]+  Stopped                 sleep 1000

	$ grep State: /proc/`pidof sleep`/status
	State:  T (stopped)

This is the "normal" behaviour, afaics the same happens with init now.

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/18, Ingo Molnar wrote:
>
> * Oleg Nesterov <oleg@redhat.com> wrote:
>
> > On 05/17, Ingo Molnar wrote:
> > >
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > > > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > > > Date		: 2009-04-09 15:43 (38 days old)
> > > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > > > 		  http://lkml.org/lkml/2009/4/10/193
> > > > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> > >
> > > Oleg says in that thread that it's as-designed, and followup
> > > questions were not replied to (yet).
> >
> > Yes, I think this is false alarm. Perhaps I missed something, and
> > I am waiting for more info from Kumar, but it looks like ltp was
> > already changed to skip the "{ PTRACE_ATTACH, 1, EPERM }" test on
> > kernels after 2.6.25
>
> Btw., why did the patch (and the revert) make any difference to the
> test? Timing differences look improbable.

Because before this series /sbin/init always ignored SIGSTOP. Now,
ptracer does PTRACE_ATTACH and exits without clearing the pending
SIGSTOP. init dequeues this signal and becomes TASK_STOPPED.

Consider:

	$ sleep 1000 &
	[1] 875

	$ grep State: /proc/`pidof sleep`/status
	State:  S (sleeping)

	$ perl -e 'syscall 101, 16, 0+shift, 0,0' `pidof sleep`    # just PTRACE_ATTACH + exit

	[1]+  Stopped                 sleep 1000

	$ grep State: /proc/`pidof sleep`/status
	State:  T (stopped)

This is the "normal" behaviour, afaics the same happens with init now.

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Mon, 18 May 2009, Ingo Molnar wrote:
> 
> Btw., why did the patch (and the revert) make any difference to the 
> test? Timing differences look improbable.

It's the change from

	!signal_group_exit(signal)

to

	!sig_kernel_only(signr)

and quite frankly, I still don't see the point.

The comment seems to be wrong too:

    If SIGSTOP/SIGKILL originate from a descendant of container-init they are
    never queued (i.e dropped in sig_ignored() in an earler patch).
    
    If SIGSTOP/SIGKILL originate from parent namespace, the signal is queued
    and container-init processes the signal.

since the bug was that the SIGSTOP (from within the same container) was 
_not_ ignored like the comment says.

			Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Mon, 18 May 2009, Ingo Molnar wrote:
> 
> Btw., why did the patch (and the revert) make any difference to the 
> test? Timing differences look improbable.

It's the change from

	!signal_group_exit(signal)

to

	!sig_kernel_only(signr)

and quite frankly, I still don't see the point.

The comment seems to be wrong too:

    If SIGSTOP/SIGKILL originate from a descendant of container-init they are
    never queued (i.e dropped in sig_ignored() in an earler patch).
    
    If SIGSTOP/SIGKILL originate from parent namespace, the signal is queued
    and container-init processes the signal.

since the bug was that the SIGSTOP (from within the same container) was 
_not_ ignored like the comment says.

			Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/18, Linus Torvalds wrote:
>
> On Mon, 18 May 2009, Ingo Molnar wrote:
> >
> > Btw., why did the patch (and the revert) make any difference to the
> > test? Timing differences look improbable.
>
> It's the change from
>
> 	!signal_group_exit(signal)
>
> to
>
> 	!sig_kernel_only(signr)
>
> and quite frankly, I still don't see the point.

Previously,

	!signal_group_exit(signal)

meant: we do not know what should we do, let's ignore this signal.
Unless the multithreaded init does exec, in this case we should
respect SIGKILL.

With the recent changes, sig_kernel_only() means: we already checked
we should handle SIGKILL/SIGSTOP when this signal was queued.

> The comment seems to be wrong too:
>
>     If SIGSTOP/SIGKILL originate from a descendant of container-init they are
>     never queued (i.e dropped in sig_ignored() in an earler patch).
>
>     If SIGSTOP/SIGKILL originate from parent namespace, the signal is queued
>     and container-init processes the signal.
>
> since the bug was that the SIGSTOP (from within the same container) was
> _not_ ignored like the comment says.

Yes, the changelog could be better because it ignores ptrace issues. But
this was discussed,

>From http://marc.info/?t=123222433100001

	Yes we should handle SIGSTOP fine if it sent from the parent namespace.

	Also. Currently it is possible to ptrace the global init, but even
	ptracer can't stop it (but ptrace_stop() works). With these patches
	ptracer can stop init.

	I forgot to mention this behaviour change, imho this side-effect
	is good.

So, at least this change is not "by accident".

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/18, Linus Torvalds wrote:
>
> On Mon, 18 May 2009, Ingo Molnar wrote:
> >
> > Btw., why did the patch (and the revert) make any difference to the
> > test? Timing differences look improbable.
>
> It's the change from
>
> 	!signal_group_exit(signal)
>
> to
>
> 	!sig_kernel_only(signr)
>
> and quite frankly, I still don't see the point.

Previously,

	!signal_group_exit(signal)

meant: we do not know what should we do, let's ignore this signal.
Unless the multithreaded init does exec, in this case we should
respect SIGKILL.

With the recent changes, sig_kernel_only() means: we already checked
we should handle SIGKILL/SIGSTOP when this signal was queued.

> The comment seems to be wrong too:
>
>     If SIGSTOP/SIGKILL originate from a descendant of container-init they are
>     never queued (i.e dropped in sig_ignored() in an earler patch).
>
>     If SIGSTOP/SIGKILL originate from parent namespace, the signal is queued
>     and container-init processes the signal.
>
> since the bug was that the SIGSTOP (from within the same container) was
> _not_ ignored like the comment says.

Yes, the changelog could be better because it ignores ptrace issues. But
this was discussed,

>From http://marc.info/?t=123222433100001

	Yes we should handle SIGSTOP fine if it sent from the parent namespace.

	Also. Currently it is possible to ptrace the global init, but even
	ptracer can't stop it (but ptrace_stop() works). With these patches
	ptracer can stop init.

	I forgot to mention this behaviour change, imho this side-effect
	is good.

So, at least this change is not "by accident".

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Oleg Nesterov]

On 05/18, Linus Torvalds wrote:
>
> On Mon, 18 May 2009, Ingo Molnar wrote:
> >
> > Btw., why did the patch (and the revert) make any difference to the
> > test? Timing differences look improbable.
>
> It's the change from
>
> 	!signal_group_exit(signal)
>
> to
>
> 	!sig_kernel_only(signr)
>
> and quite frankly, I still don't see the point.

Previously,

	!signal_group_exit(signal)

meant: we do not know what should we do, let's ignore this signal.
Unless the multithreaded init does exec, in this case we should
respect SIGKILL.

With the recent changes, sig_kernel_only() means: we already checked
we should handle SIGKILL/SIGSTOP when this signal was queued.

> The comment seems to be wrong too:
>
>     If SIGSTOP/SIGKILL originate from a descendant of container-init they are
>     never queued (i.e dropped in sig_ignored() in an earler patch).
>
>     If SIGSTOP/SIGKILL originate from parent namespace, the signal is queued
>     and container-init processes the signal.
>
> since the bug was that the SIGSTOP (from within the same container) was
> _not_ ignored like the comment says.

Yes, the changelog could be better because it ignores ptrace issues. But
this was discussed,

From http://marc.info/?t=123222433100001

	Yes we should handle SIGSTOP fine if it sent from the parent namespace.

	Also. Currently it is possible to ptrace the global init, but even
	ptracer can't stop it (but ptrace_stop() works). With these patches
	ptracer can stop init.

	I forgot to mention this behaviour change, imho this side-effect
	is good.

So, at least this change is not "by accident".

Oleg.

Re: [Bug #13188] horizontal strips of the screen frozen

[Justin Madru]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> Subject		: horizontal strips of the screen frozen
> Submitter	: Justin Madru <jdm64@gawab.com>
> Date		: 2009-04-24 20:59 (23 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
>
>
>
>   
As far as I can tell, this seams to be fixed by the intel-2.7.1 driver, 
and the bug only happened with UXA.
I did some minor testing and I couldn't trigger the bug. (earlier 
discussion in http://lkml.org/lkml/2009/4/23/587)
So this seams to be a user space bug, fixed in the intel-2.7.1 bug fix 
release (intel-2.7.0 still has the issue).

Justin Madru

Re: [Bug #13188] horizontal strips of the screen frozen

[Justin Madru]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> Subject		: horizontal strips of the screen frozen
> Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-04-24 20:59 (23 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
>
>
>
>   
As far as I can tell, this seams to be fixed by the intel-2.7.1 driver, 
and the bug only happened with UXA.
I did some minor testing and I couldn't trigger the bug. (earlier 
discussion in http://lkml.org/lkml/2009/4/23/587)
So this seams to be a user space bug, fixed in the intel-2.7.1 bug fix 
release (intel-2.7.0 still has the issue).

Justin Madru

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Bartlomiej Zolnierkiewicz]

On Sunday 17 May 2009 18:19:16 Borislav Petkov wrote:
> Hi,
> 
> On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> > On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > > Submitter	: rob <rob1@housetosell.net>
> > > > Date		: 2009-05-12 19:34 (5 days old)
> > > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > > 
> > > tainted crash, but probably legit. It does show some badness in an 
> > > old-IDE legacy codepath:
> > > 
> > > [<c0371865>] error_code+0x65/0x6c
> > > [<c0110155>] do_page_fault+0x0/0x1e0
> > > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > > [<c027dcc2>] ide_intr+0x109/0x161
> > > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > > [<c013354a>] handle_level_irq+0x4f/0x85
> > > [<c0103df7>] handle_irq+0x17/0x20
> > > [<c0103da5>] do_IRQ+0x2b/0x66
> > > [<c0102be9>] common_interupt+0x29/0x30
> > > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > > [<c0106db3>] default_idle+0x25/0x38
> > > [<c01019be>] cpu_idle+0x19/0x2d
> > > [<c0468907>] start_kernel+0x23f/0x242
> > > 
> > > report subject line is too unspecific, it should be changed to 
> > > something like:
> > > 
> > >   legacy IDE cmd40x related bootup crash
> > 
> > 
> > It seems the crash has been rewritten by hand. I don't see
> > any cmd40x_init(), I guess it's about cmd640 chipset, then
> > cmd640x_init()

Frederic, is the oops reproducible?  Is 2.6.30-rc6 any better?

Does it help if you disable CONFIG_BLK_DEV_CMD640?
(this system doesn't have CMD640 chipset)

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Bartlomiej Zolnierkiewicz]

On Sunday 17 May 2009 18:19:16 Borislav Petkov wrote:
> Hi,
> 
> On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> > On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > > Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
> > > > Date		: 2009-05-12 19:34 (5 days old)
> > > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > > 
> > > tainted crash, but probably legit. It does show some badness in an 
> > > old-IDE legacy codepath:
> > > 
> > > [<c0371865>] error_code+0x65/0x6c
> > > [<c0110155>] do_page_fault+0x0/0x1e0
> > > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > > [<c027dcc2>] ide_intr+0x109/0x161
> > > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > > [<c013354a>] handle_level_irq+0x4f/0x85
> > > [<c0103df7>] handle_irq+0x17/0x20
> > > [<c0103da5>] do_IRQ+0x2b/0x66
> > > [<c0102be9>] common_interupt+0x29/0x30
> > > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > > [<c0106db3>] default_idle+0x25/0x38
> > > [<c01019be>] cpu_idle+0x19/0x2d
> > > [<c0468907>] start_kernel+0x23f/0x242
> > > 
> > > report subject line is too unspecific, it should be changed to 
> > > something like:
> > > 
> > >   legacy IDE cmd40x related bootup crash
> > 
> > 
> > It seems the crash has been rewritten by hand. I don't see
> > any cmd40x_init(), I guess it's about cmd640 chipset, then
> > cmd640x_init()

Frederic, is the oops reproducible?  Is 2.6.30-rc6 any better?

Does it help if you disable CONFIG_BLK_DEV_CMD640?
(this system doesn't have CMD640 chipset)

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Sukadev Bhattiprolu]

Oleg Nesterov [oleg@redhat.com] wrote:
| Sorry for delay, I had a vacation.
| 
| On 05/17, Linus Torvalds wrote:
| >
| > On Sat, 16 May 2009, Rafael J. Wysocki wrote:
| > >
| > > This message has been generated automatically as a part of a report
| > > of recent regressions.
| > >
| > > The following bug entry is on the current list of known regressions
| > > from 2.6.29.  Please verify if it still should be listed and let me know
| > > (either way).
| > >
| > >
| > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
| > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
| > > Submitter	: Kumar Gala <galak@kernel.crashing.org>
| > > Date		: 2009-04-09 15:43 (38 days old)
| > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
| > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
| > > 		  http://lkml.org/lkml/2009/4/10/193
| > > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
| >
| > I think we have to revert that thing. I haven't heard of any fixes to that
| > commit.
| 
| I thought this was already resolved.

Yes, so did I. We had asked for more info/confirmation before, most recently
on Apr 25 http://lkml.org/lkml/2009/4/25/132, although finding the LTP
test like below would have helped :-)

| 
| And I don't think the kernel is buggy, this is expected behaviour. With
| this commit (actually, there were several patches) /sbin/init respects
| SIGSTOP if the caller has rights to send it, this change is intentional.
| I'd even say this is fix.
| 
| Note that even root can't stop init, SIGSTOP should be sent from the
| parent namespace, or from ptracer. And ptracer could obviously ptrace_stop()
| init even before this patch.
| 
| 
| But, Kumar, could you please provide more info? I downloaded
| ltp-full-20081130.tgz, and I see that ptrace03.c does:

I beleive Kumar was running an older version of LTP (20080131)

| 
|                         /* since Linux 2.6.26, it's allowed to trace init,
|                            so just skip this test case */
|                         if (i == 0 && tst_kvercmp(2,6,25) > 0) {
|                                 tst_resm(TCONF,
|                                          "this kernel allows to trace init");
|                                 continue;
|                         }
| 
| So, could you explain which test traces init?
| 
| Oleg.

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Sukadev Bhattiprolu]

Oleg Nesterov [oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org] wrote:
| Sorry for delay, I had a vacation.
| 
| On 05/17, Linus Torvalds wrote:
| >
| > On Sat, 16 May 2009, Rafael J. Wysocki wrote:
| > >
| > > This message has been generated automatically as a part of a report
| > > of recent regressions.
| > >
| > > The following bug entry is on the current list of known regressions
| > > from 2.6.29.  Please verify if it still should be listed and let me know
| > > (either way).
| > >
| > >
| > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
| > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
| > > Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
| > > Date		: 2009-04-09 15:43 (38 days old)
| > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
| > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
| > > 		  http://lkml.org/lkml/2009/4/10/193
| > > Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
| >
| > I think we have to revert that thing. I haven't heard of any fixes to that
| > commit.
| 
| I thought this was already resolved.

Yes, so did I. We had asked for more info/confirmation before, most recently
on Apr 25 http://lkml.org/lkml/2009/4/25/132, although finding the LTP
test like below would have helped :-)

| 
| And I don't think the kernel is buggy, this is expected behaviour. With
| this commit (actually, there were several patches) /sbin/init respects
| SIGSTOP if the caller has rights to send it, this change is intentional.
| I'd even say this is fix.
| 
| Note that even root can't stop init, SIGSTOP should be sent from the
| parent namespace, or from ptracer. And ptracer could obviously ptrace_stop()
| init even before this patch.
| 
| 
| But, Kumar, could you please provide more info? I downloaded
| ltp-full-20081130.tgz, and I see that ptrace03.c does:

I beleive Kumar was running an older version of LTP (20080131)

| 
|                         /* since Linux 2.6.26, it's allowed to trace init,
|                            so just skip this test case */
|                         if (i == 0 && tst_kvercmp(2,6,25) > 0) {
|                                 tst_resm(TCONF,
|                                          "this kernel allows to trace init");
|                                 continue;
|                         }
| 
| So, could you explain which test traces init?
| 
| Oleg.

Re: [Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

On Monday 18 May 2009, Justin Madru wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> > Subject		: horizontal strips of the screen frozen
> > Submitter	: Justin Madru <jdm64@gawab.com>
> > Date		: 2009-04-24 20:59 (23 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> > References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
> >
> >
> >
> >   
> As far as I can tell, this seams to be fixed by the intel-2.7.1 driver, 
> and the bug only happened with UXA.
> I did some minor testing and I couldn't trigger the bug. (earlier 
> discussion in http://lkml.org/lkml/2009/4/23/587)
> So this seams to be a user space bug, fixed in the intel-2.7.1 bug fix 
> release (intel-2.7.0 still has the issue).

I have closed the bug.

Thanks,
Rafael

Re: [Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

On Monday 18 May 2009, Justin Madru wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> > Subject		: horizontal strips of the screen frozen
> > Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-04-24 20:59 (23 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> > References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
> >
> >
> >
> >   
> As far as I can tell, this seams to be fixed by the intel-2.7.1 driver, 
> and the bug only happened with UXA.
> I did some minor testing and I couldn't trigger the bug. (earlier 
> discussion in http://lkml.org/lkml/2009/4/23/587)
> So this seams to be a user space bug, fixed in the intel-2.7.1 bug fix 
> release (intel-2.7.0 still has the issue).

I have closed the bug.

Thanks,
Rafael

Re: [Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

On Monday 18 May 2009, Justin Madru wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> > Subject		: horizontal strips of the screen frozen
> > Submitter	: Justin Madru <jdm64@gawab.com>
> > Date		: 2009-04-24 20:59 (23 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> > References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
> >
> >
> >
> >   
> As far as I can tell, this seams to be fixed by the intel-2.7.1 driver, 
> and the bug only happened with UXA.
> I did some minor testing and I couldn't trigger the bug. (earlier 
> discussion in http://lkml.org/lkml/2009/4/23/587)
> So this seams to be a user space bug, fixed in the intel-2.7.1 bug fix 
> release (intel-2.7.0 still has the issue).

I have closed the bug.

Thanks,
Rafael

Re: [Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

On Monday 18 May 2009, Justin Madru wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> > Subject		: horizontal strips of the screen frozen
> > Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-04-24 20:59 (23 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> > References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
> >
> >
> >
> >   
> As far as I can tell, this seams to be fixed by the intel-2.7.1 driver, 
> and the bug only happened with UXA.
> I did some minor testing and I couldn't trigger the bug. (earlier 
> discussion in http://lkml.org/lkml/2009/4/23/587)
> So this seams to be a user space bug, fixed in the intel-2.7.1 bug fix 
> release (intel-2.7.0 still has the issue).

I have closed the bug.

Thanks,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Borislav Petkov]

Hi,

On Mon, May 18, 2009 at 06:35:28PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 17 May 2009 18:19:16 Borislav Petkov wrote:
> > Hi,
> > 
> > On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> > > On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > > > Submitter	: rob <rob1@housetosell.net>
> > > > > Date		: 2009-05-12 19:34 (5 days old)
> > > > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > > > 
> > > > tainted crash, but probably legit. It does show some badness in an 
> > > > old-IDE legacy codepath:
> > > > 
> > > > [<c0371865>] error_code+0x65/0x6c
> > > > [<c0110155>] do_page_fault+0x0/0x1e0
> > > > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > > > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > > > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > > > [<c027dcc2>] ide_intr+0x109/0x161
> > > > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > > > [<c013354a>] handle_level_irq+0x4f/0x85
> > > > [<c0103df7>] handle_irq+0x17/0x20
> > > > [<c0103da5>] do_IRQ+0x2b/0x66
> > > > [<c0102be9>] common_interupt+0x29/0x30
> > > > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > > > [<c0106db3>] default_idle+0x25/0x38
> > > > [<c01019be>] cpu_idle+0x19/0x2d
> > > > [<c0468907>] start_kernel+0x23f/0x242
> > > > 
> > > > report subject line is too unspecific, it should be changed to 
> > > > something like:
> > > > 
> > > >   legacy IDE cmd40x related bootup crash
> > > 
> > > 
> > > It seems the crash has been rewritten by hand. I don't see
> > > any cmd40x_init(), I guess it's about cmd640 chipset, then
> > > cmd640x_init()

No, you don't because its a via82cxxx chipset. I've CC'ed the bug
reporter's mail to linux-ide, see

http://marc.info/?l=linux-ide&m=124271263912107&w=2

-- 
Regards/Gruss,
    Boris.

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Ingo Molnar]

* Oleg Nesterov <oleg@redhat.com> wrote:

> Sorry for delay, I had a vacation.
> 
> On 05/17, Linus Torvalds wrote:
> >
> > On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> > >
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > >
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.29.  Please verify if it still should be listed and let me know
> > > (either way).
> > >
> > >
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > > Date		: 2009-04-09 15:43 (38 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > > 		  http://lkml.org/lkml/2009/4/10/193
> > > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> >
> > I think we have to revert that thing. I haven't heard of any fixes to that
> > commit.
> 
> I thought this was already resolved.
> 
> And I don't think the kernel is buggy, this is expected behaviour. 
> With this commit (actually, there were several patches) /sbin/init 
> respects SIGSTOP if the caller has rights to send it, this change 
> is intentional. I'd even say this is fix.
> 
> Note that even root can't stop init, SIGSTOP should be sent from 
> the parent namespace, or from ptracer. And ptracer could obviously 
> ptrace_stop() init even before this patch.

There's one important aspect here: _if_ a change results in 
user-space visible behavioral change, it does not matter how correct 
it is in the grand scheme of things. (beyond plain bugfixes solving 
crashes, etc.) What matters is whether there's any app out there 
that might possibly rely on the old behavior.

The LTP testcase might be synthetic, and it could be fixed and the 
commit might even end up being correct - but some thought should be 
expended on compatibility and real-life impact (and scope) here - 
not just on strict 'correctness'.

	Ingo

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Ingo Molnar]

* Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

> Sorry for delay, I had a vacation.
> 
> On 05/17, Linus Torvalds wrote:
> >
> > On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> > >
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > >
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.29.  Please verify if it still should be listed and let me know
> > > (either way).
> > >
> > >
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > > Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
> > > Date		: 2009-04-09 15:43 (38 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > > 		  http://lkml.org/lkml/2009/4/10/193
> > > Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> >
> > I think we have to revert that thing. I haven't heard of any fixes to that
> > commit.
> 
> I thought this was already resolved.
> 
> And I don't think the kernel is buggy, this is expected behaviour. 
> With this commit (actually, there were several patches) /sbin/init 
> respects SIGSTOP if the caller has rights to send it, this change 
> is intentional. I'd even say this is fix.
> 
> Note that even root can't stop init, SIGSTOP should be sent from 
> the parent namespace, or from ptracer. And ptracer could obviously 
> ptrace_stop() init even before this patch.

There's one important aspect here: _if_ a change results in 
user-space visible behavioral change, it does not matter how correct 
it is in the grand scheme of things. (beyond plain bugfixes solving 
crashes, etc.) What matters is whether there's any app out there 
that might possibly rely on the old behavior.

The LTP testcase might be synthetic, and it could be fixed and the 
commit might even end up being correct - but some thought should be 
expended on compatibility and real-life impact (and scope) here - 
not just on strict 'correctness'.

	Ingo

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Oleg Nesterov]

On 05/19, Ingo Molnar wrote:
>
> * Oleg Nesterov <oleg@redhat.com> wrote:
>
> > And I don't think the kernel is buggy, this is expected behaviour.
> > With this commit (actually, there were several patches) /sbin/init
> > respects SIGSTOP if the caller has rights to send it, this change
> > is intentional. I'd even say this is fix.
> >
> > Note that even root can't stop init, SIGSTOP should be sent from
> > the parent namespace, or from ptracer. And ptracer could obviously
> > ptrace_stop() init even before this patch.
>
> There's one important aspect here: _if_ a change results in
> user-space visible behavioral change, it does not matter how correct
> it is in the grand scheme of things. (beyond plain bugfixes solving
> crashes, etc.) What matters is whether there's any app out there
> that might possibly rely on the old behavior.
>
> The LTP testcase might be synthetic, and it could be fixed and the
> commit might even end up being correct - but some thought should be
> expended on compatibility and real-life impact (and scope) here -
> not just on strict 'correctness'.

Yes, agreed.

But hopefully in this case we can't break the user-space. Because the
tracing of /sbin/init is special, and this was forbidden till 2.6.25.
Not only you can make the system unusable, it is very easy to crash
the kernel if you trace init. I don't think any "good" app can rely
on the wrong old behaviour, but of course any behavioral change is
dangerous.

And please note that the old behaviour was known to be wrong. If we
take the sub-namespace inits into account, it was very wrong. Of course,
we can add the special is_global_init() hack to preserve the current
behaviour at least for the root namespace, but this doesn't look good.

Oleg.

Re: [Bug #13107] LTP 20080131 causes defunct processes w/2.6.30-rc1

[Oleg Nesterov]

On 05/19, Ingo Molnar wrote:
>
> * Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>
> > And I don't think the kernel is buggy, this is expected behaviour.
> > With this commit (actually, there were several patches) /sbin/init
> > respects SIGSTOP if the caller has rights to send it, this change
> > is intentional. I'd even say this is fix.
> >
> > Note that even root can't stop init, SIGSTOP should be sent from
> > the parent namespace, or from ptracer. And ptracer could obviously
> > ptrace_stop() init even before this patch.
>
> There's one important aspect here: _if_ a change results in
> user-space visible behavioral change, it does not matter how correct
> it is in the grand scheme of things. (beyond plain bugfixes solving
> crashes, etc.) What matters is whether there's any app out there
> that might possibly rely on the old behavior.
>
> The LTP testcase might be synthetic, and it could be fixed and the
> commit might even end up being correct - but some thought should be
> expended on compatibility and real-life impact (and scope) here -
> not just on strict 'correctness'.

Yes, agreed.

But hopefully in this case we can't break the user-space. Because the
tracing of /sbin/init is special, and this was forbidden till 2.6.25.
Not only you can make the system unusable, it is very easy to crash
the kernel if you trace init. I don't think any "good" app can rely
on the wrong old behaviour, but of course any behavioral change is
dangerous.

And please note that the old behaviour was known to be wrong. If we
take the sub-namespace inits into account, it was very wrong. Of course,
we can add the special is_global_init() hack to preserve the current
behaviour at least for the root namespace, but this doesn't look good.

Oleg.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frederic Weisbecker]

On Mon, May 18, 2009 at 06:35:28PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 17 May 2009 18:19:16 Borislav Petkov wrote:
> > Hi,
> > 
> > On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> > > On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > > > Submitter	: rob <rob1@housetosell.net>
> > > > > Date		: 2009-05-12 19:34 (5 days old)
> > > > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > > > 
> > > > tainted crash, but probably legit. It does show some badness in an 
> > > > old-IDE legacy codepath:
> > > > 
> > > > [<c0371865>] error_code+0x65/0x6c
> > > > [<c0110155>] do_page_fault+0x0/0x1e0
> > > > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > > > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > > > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > > > [<c027dcc2>] ide_intr+0x109/0x161
> > > > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > > > [<c013354a>] handle_level_irq+0x4f/0x85
> > > > [<c0103df7>] handle_irq+0x17/0x20
> > > > [<c0103da5>] do_IRQ+0x2b/0x66
> > > > [<c0102be9>] common_interupt+0x29/0x30
> > > > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > > > [<c0106db3>] default_idle+0x25/0x38
> > > > [<c01019be>] cpu_idle+0x19/0x2d
> > > > [<c0468907>] start_kernel+0x23f/0x242
> > > > 
> > > > report subject line is too unspecific, it should be changed to 
> > > > something like:
> > > > 
> > > >   legacy IDE cmd40x related bootup crash
> > > 
> > > 
> > > It seems the crash has been rewritten by hand. I don't see
> > > any cmd40x_init(), I guess it's about cmd640 chipset, then
> > > cmd640x_init()
> 
> Frederic, is the oops reproducible?  Is 2.6.30-rc6 any better?
> 
> Does it help if you disable CONFIG_BLK_DEV_CMD640?
> (this system doesn't have CMD640 chipset)


Sorry, I'm not the author of this bug report and I don't have this
hardware. I've just added you in Cc's :-)

But I'm adding the bug reporter in Cc.

Rob, could you test above Bartlomiej's suggestion?

Thanks,

Frederic.

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frederic Weisbecker]

On Mon, May 18, 2009 at 06:35:28PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 17 May 2009 18:19:16 Borislav Petkov wrote:
> > Hi,
> > 
> > On Sun, May 17, 2009 at 03:32:11PM +0200, Frederic Weisbecker wrote:
> > > On Sun, May 17, 2009 at 09:33:27AM +0200, Ingo Molnar wrote:
> > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > > > > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > > > > Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
> > > > > Date		: 2009-05-12 19:34 (5 days old)
> > > > > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> > > > 
> > > > tainted crash, but probably legit. It does show some badness in an 
> > > > old-IDE legacy codepath:
> > > > 
> > > > [<c0371865>] error_code+0x65/0x6c
> > > > [<c0110155>] do_page_fault+0x0/0x1e0
> > > > [<c027dafc>] ide_complete_rq+0xf/0x3b
> > > > [<c02870a0>] cdrom_newpc_intr+0x64d/0x6cd
> > > > [<c0286a53>] cdrom_newpc_intr+0x0/0x6cd
> > > > [<c027dcc2>] ide_intr+0x109/0x161
> > > > [<c0132298>] handle_IRQ_event+0x54/0xc7
> > > > [<c013354a>] handle_level_irq+0x4f/0x85
> > > > [<c0103df7>] handle_irq+0x17/0x20
> > > > [<c0103da5>] do_IRQ+0x2b/0x66
> > > > [<c0102be9>] common_interupt+0x29/0x30
> > > > [<c0480000>] cmd40x_init+0x2ac/0x38d
> > > > [<c0106db3>] default_idle+0x25/0x38
> > > > [<c01019be>] cpu_idle+0x19/0x2d
> > > > [<c0468907>] start_kernel+0x23f/0x242
> > > > 
> > > > report subject line is too unspecific, it should be changed to 
> > > > something like:
> > > > 
> > > >   legacy IDE cmd40x related bootup crash
> > > 
> > > 
> > > It seems the crash has been rewritten by hand. I don't see
> > > any cmd40x_init(), I guess it's about cmd640 chipset, then
> > > cmd640x_init()
> 
> Frederic, is the oops reproducible?  Is 2.6.30-rc6 any better?
> 
> Does it help if you disable CONFIG_BLK_DEV_CMD640?
> (this system doesn't have CMD640 chipset)


Sorry, I'm not the author of this bug report and I don't have this
hardware. I've just added you in Cc's :-)

But I'm adding the bug reporter in Cc.

Rob, could you test above Bartlomiej's suggestion?

Thanks,

Frederic.

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Larry Finger]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
> Subject		: Page allocation failures with b43 and p54usb
> Submitter	: Larry Finger <Larry.Finger@lwfinger.net>
> Date		: 2009-04-29 21:01 (18 days old)
> References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
> Handled-By	: Johannes Berg <johannes@sipsolutions.net>

I have been unable to repeat the problem with recent kernels - I am now running
2.6.30-rc6. This regression should probably be dropped even though it may show
up when 2.6.30 is released.

Larry

Re: [Bug #13319] Page allocation failures with b43 and p54usb

[Larry Finger]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13319
> Subject		: Page allocation failures with b43 and p54usb
> Submitter	: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
> Date		: 2009-04-29 21:01 (18 days old)
> References	: http://marc.info/?l=linux-kernel&m=124103897101088&w=4
> Handled-By	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

I have been unable to repeat the problem with recent kernels - I am now running
2.6.30-rc6. This regression should probably be dropped even though it may show
up when 2.6.30 is released.

Larry

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
> Subject		: cifs_close: NULL pointer dereference
> Submitter	: Luca Tettamanti <kronos.it@gmail.com>
> Date		: 2009-05-16 16:28 (1 days old)
> References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4

Fixed by 703a3b8e5c01cf6fb33c6d8dc99905f889a4e992.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
> Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
> Submitter	: Ferenc Wagner <wferi@niif.hu>
> Date		: 2009-05-12 21:28 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4

Fixed by 9a2845c453d170e4e9b1437fa671dbf39b0e7bd8.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> Subject		: kernel panic -  not syncing : fatel exception in interupt
> Submitter	: rob <rob1@housetosell.net>
> Date		: 2009-05-12 19:34 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

This should be fixed by e3b29f05124b07303088795396ff858811d2acb8.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
> Subject		: 2.6.30-rc2-git7 build problem
> Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
> Date		: 2009-04-21 13:39 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
> 		  http://lkml.org/lkml/2009/4/27/56

This one really looks like a compiler bug (the undefined symbol is an 
internal gcc one: ".L192"). And the driver that gets it (kl5kusb105) has 
not actually had any changes since 2.6.29 - although header files that it 
includes obviously do have some, so it's entirely possible that some 
infrastructure change causes it to trigger.

Martin hit another bug with his compiler (an ICE in gcc, fixed by commit 
26a9a418237c0b06528941bca693c49c8d97edbe), which is why I'm so willing to 
blame that.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

This one seems to have become "not-a-bug". Yes, LTP used to check that you 
cannot send SIGSTP to init, but people do want to send signals to init 
(especially when they are inside pid-namespace containers), and as long as 
it's only a LTP test that already got modified (and not some actual 
real-life usage), I'm considering this a "test failed because it was 
testing for behavior that we want to change" at least for now.

				Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Linus Torvalds]

On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
> Subject		: cifs_close: NULL pointer dereference
> Submitter	: Luca Tettamanti <kronos.it@gmail.com>
> Date		: 2009-05-16 16:28 (1 days old)
> References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4

Fixed by 703a3b8e5c01cf6fb33c6d8dc99905f889a4e992.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
> Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
> Submitter	: Ferenc Wagner <wferi@niif.hu>
> Date		: 2009-05-12 21:28 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4

Fixed by 9a2845c453d170e4e9b1437fa671dbf39b0e7bd8.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> Subject		: kernel panic -  not syncing : fatel exception in interupt
> Submitter	: rob <rob1@housetosell.net>
> Date		: 2009-05-12 19:34 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4

This should be fixed by e3b29f05124b07303088795396ff858811d2acb8.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
> Subject		: 2.6.30-rc2-git7 build problem
> Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
> Date		: 2009-04-21 13:39 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
> 		  http://lkml.org/lkml/2009/4/27/56

This one really looks like a compiler bug (the undefined symbol is an 
internal gcc one: ".L192"). And the driver that gets it (kl5kusb105) has 
not actually had any changes since 2.6.29 - although header files that it 
includes obviously do have some, so it's entirely possible that some 
infrastructure change causes it to trigger.

Martin hit another bug with his compiler (an ICE in gcc, fixed by commit 
26a9a418237c0b06528941bca693c49c8d97edbe), which is why I'm so willing to 
blame that.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> Submitter	: Kumar Gala <galak@kernel.crashing.org>
> Date		: 2009-04-09 15:43 (38 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> 		  http://lkml.org/lkml/2009/4/10/193
> Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>

This one seems to have become "not-a-bug". Yes, LTP used to check that you 
cannot send SIGSTP to init, but people do want to send signals to init 
(especially when they are inside pid-namespace containers), and as long as 
it's only a LTP test that already got modified (and not some actual 
real-life usage), I'm considering this a "test failed because it was 
testing for behavior that we want to change" at least for now.

				Linus

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Friday 22 May 2009, Linus Torvalds wrote:
> 
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
> > Subject		: cifs_close: NULL pointer dereference
> > Submitter	: Luca Tettamanti <kronos.it@gmail.com>
> > Date		: 2009-05-16 16:28 (1 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4
> 
> Fixed by 703a3b8e5c01cf6fb33c6d8dc99905f889a4e992.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
> > Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
> > Submitter	: Ferenc Wagner <wferi@niif.hu>
> > Date		: 2009-05-12 21:28 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4
> 
> Fixed by 9a2845c453d170e4e9b1437fa671dbf39b0e7bd8.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1@housetosell.net>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> This should be fixed by e3b29f05124b07303088795396ff858811d2acb8.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
> > Subject		: 2.6.30-rc2-git7 build problem
> > Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
> > Date		: 2009-04-21 13:39 (26 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
> > 		  http://lkml.org/lkml/2009/4/27/56
> 
> This one really looks like a compiler bug (the undefined symbol is an 
> internal gcc one: ".L192"). And the driver that gets it (kl5kusb105) has 
> not actually had any changes since 2.6.29 - although header files that it 
> includes obviously do have some, so it's entirely possible that some 
> infrastructure change causes it to trigger.
> 
> Martin hit another bug with his compiler (an ICE in gcc, fixed by commit 
> 26a9a418237c0b06528941bca693c49c8d97edbe), which is why I'm so willing to 
> blame that.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> 
> This one seems to have become "not-a-bug". Yes, LTP used to check that you 
> cannot send SIGSTP to init, but people do want to send signals to init 
> (especially when they are inside pid-namespace containers), and as long as 
> it's only a LTP test that already got modified (and not some actual 
> real-life usage), I'm considering this a "test failed because it was 
> testing for behavior that we want to change" at least for now.

Thanks a lot, this really helps! :-)

I've closed all of the bugs above.

Best,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Friday 22 May 2009, Linus Torvalds wrote:
> 
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
> > Subject		: cifs_close: NULL pointer dereference
> > Submitter	: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-05-16 16:28 (1 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4
> 
> Fixed by 703a3b8e5c01cf6fb33c6d8dc99905f889a4e992.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
> > Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
> > Submitter	: Ferenc Wagner <wferi-eEbw3PyuezQ@public.gmane.org>
> > Date		: 2009-05-12 21:28 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4
> 
> Fixed by 9a2845c453d170e4e9b1437fa671dbf39b0e7bd8.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1-z2Ut7v/pTR/vt0rt8C/ehw@public.gmane.org>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> This should be fixed by e3b29f05124b07303088795396ff858811d2acb8.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
> > Subject		: 2.6.30-rc2-git7 build problem
> > Submitter	: Martin Knoblauch <spamtrap-Ys4E+72pFW0hFhg+JK9F0w@public.gmane.org>
> > Date		: 2009-04-21 13:39 (26 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
> > 		  http://lkml.org/lkml/2009/4/27/56
> 
> This one really looks like a compiler bug (the undefined symbol is an 
> internal gcc one: ".L192"). And the driver that gets it (kl5kusb105) has 
> not actually had any changes since 2.6.29 - although header files that it 
> includes obviously do have some, so it's entirely possible that some 
> infrastructure change causes it to trigger.
> 
> Martin hit another bug with his compiler (an ICE in gcc, fixed by commit 
> 26a9a418237c0b06528941bca693c49c8d97edbe), which is why I'm so willing to 
> blame that.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> 
> This one seems to have become "not-a-bug". Yes, LTP used to check that you 
> cannot send SIGSTP to init, but people do want to send signals to init 
> (especially when they are inside pid-namespace containers), and as long as 
> it's only a LTP test that already got modified (and not some actual 
> real-life usage), I'm considering this a "test failed because it was 
> testing for behavior that we want to change" at least for now.

Thanks a lot, this really helps! :-)

I've closed all of the bugs above.

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

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Friday 22 May 2009, Linus Torvalds wrote:
> 
> On Sat, 16 May 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13329
> > Subject		: cifs_close: NULL pointer dereference
> > Submitter	: Luca Tettamanti <kronos.it@gmail.com>
> > Date		: 2009-05-16 16:28 (1 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124249133701702&w=4
> 
> Fixed by 703a3b8e5c01cf6fb33c6d8dc99905f889a4e992.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13298
> > Subject		: modprobe ipmi_si hangs under 2.6.30-rc5
> > Submitter	: Ferenc Wagner <wferi@niif.hu>
> > Date		: 2009-05-12 21:28 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216379407177&w=4
> 
> Fixed by 9a2845c453d170e4e9b1437fa671dbf39b0e7bd8.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13297
> > Subject		: kernel panic -  not syncing : fatel exception in interupt
> > Submitter	: rob <rob1@housetosell.net>
> > Date		: 2009-05-12 19:34 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124216126903309&w=4
> 
> This should be fixed by e3b29f05124b07303088795396ff858811d2acb8.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13177
> > Subject		: 2.6.30-rc2-git7 build problem
> > Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
> > Date		: 2009-04-21 13:39 (26 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124032163602132&w=4
> > 		  http://lkml.org/lkml/2009/4/27/56
> 
> This one really looks like a compiler bug (the undefined symbol is an 
> internal gcc one: ".L192"). And the driver that gets it (kl5kusb105) has 
> not actually had any changes since 2.6.29 - although header files that it 
> includes obviously do have some, so it's entirely possible that some 
> infrastructure change causes it to trigger.
> 
> Martin hit another bug with his compiler (an ICE in gcc, fixed by commit 
> 26a9a418237c0b06528941bca693c49c8d97edbe), which is why I'm so willing to 
> blame that.
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13107
> > Subject		: LTP 20080131 causes defunct processes w/2.6.30-rc1
> > Submitter	: Kumar Gala <galak@kernel.crashing.org>
> > Date		: 2009-04-09 15:43 (38 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b3bfa0cba867f23365b81658b47efd906830879b
> > References	: http://marc.info/?l=linux-kernel&m=123929187208953&w=4
> > 		  http://lkml.org/lkml/2009/4/10/193
> > Handled-By	: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> 
> This one seems to have become "not-a-bug". Yes, LTP used to check that you 
> cannot send SIGSTP to init, but people do want to send signals to init 
> (especially when they are inside pid-namespace containers), and as long as 
> it's only a LTP test that already got modified (and not some actual 
> real-life usage), I'm considering this a "test failed because it was 
> testing for behavior that we want to change" at least for now.

Thanks a lot, this really helps! :-)

I've closed all of the bugs above.

Best,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frans Pop]

Rafael J. Wysocki wrote:
> If you know of any other unresolved regressions from 2.6.29, please let
> me know either and I'll add them to the list.

It may be worth tracking a possible regression introduced with -rc6 as a 
result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.

A new warning that was added in drivers/acpi/processor_throttling.c 
(commit 4973b22a: 'ACPI processor: reset the throttling state once it's 
invalid') may be triggering in cases where it shouldn't. It seems to 
trigger during boot and on 'cat /proc/acpi/processor/*/throttling'.
Otherwise it's probably relatively harmless.

See the comments starting at #23 for details.

Cheers,
FJP

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frans Pop]

Rafael J. Wysocki wrote:
> If you know of any other unresolved regressions from 2.6.29, please let
> me know either and I'll add them to the list.

It may be worth tracking a possible regression introduced with -rc6 as a 
result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.

A new warning that was added in drivers/acpi/processor_throttling.c 
(commit 4973b22a: 'ACPI processor: reset the throttling state once it's 
invalid') may be triggering in cases where it shouldn't. It seems to 
trigger during boot and on 'cat /proc/acpi/processor/*/throttling'.
Otherwise it's probably relatively harmless.

See the comments starting at #23 for details.

Cheers,
FJP

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Monday 25 May 2009, Frans Pop wrote:
> Rafael J. Wysocki wrote:
> > If you know of any other unresolved regressions from 2.6.29, please let
> > me know either and I'll add them to the list.
> 
> It may be worth tracking a possible regression introduced with -rc6 as a 
> result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.
> 
> A new warning that was added in drivers/acpi/processor_throttling.c 
> (commit 4973b22a: 'ACPI processor: reset the throttling state once it's 
> invalid') may be triggering in cases where it shouldn't. It seems to 
> trigger during boot and on 'cat /proc/acpi/processor/*/throttling'.
> Otherwise it's probably relatively harmless.
> 
> See the comments starting at #23 for details.

Hmm.  It's really better if you file a separate bug for that with a reference
to the previous discussion.

Thanks,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Monday 25 May 2009, Frans Pop wrote:
> Rafael J. Wysocki wrote:
> > If you know of any other unresolved regressions from 2.6.29, please let
> > me know either and I'll add them to the list.
> 
> It may be worth tracking a possible regression introduced with -rc6 as a 
> result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.
> 
> A new warning that was added in drivers/acpi/processor_throttling.c 
> (commit 4973b22a: 'ACPI processor: reset the throttling state once it's 
> invalid') may be triggering in cases where it shouldn't. It seems to 
> trigger during boot and on 'cat /proc/acpi/processor/*/throttling'.
> Otherwise it's probably relatively harmless.
> 
> See the comments starting at #23 for details.

Hmm.  It's really better if you file a separate bug for that with a reference
to the previous discussion.

Thanks,
Rafael

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Frans Pop]

On Tuesday 26 May 2009, Rafael J. Wysocki wrote:
> On Monday 25 May 2009, Frans Pop wrote:
> > Rafael J. Wysocki wrote:
> > > If you know of any other unresolved regressions from 2.6.29, please
> > > let me know either and I'll add them to the list.
> >
> > It may be worth tracking a possible regression introduced with -rc6
> > as a result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.
> >
> > A new warning that was added in drivers/acpi/processor_throttling.c
> > (commit 4973b22a: 'ACPI processor: reset the throttling state once
> > it's invalid') may be triggering in cases where it shouldn't. It
> > seems to trigger during boot and on 'cat
> > /proc/acpi/processor/*/throttling'. Otherwise it's probably
> > relatively harmless.
> >
> > See the comments starting at #23 for details.
>
> Hmm.  It's really better if you file a separate bug for that with a
> reference to the previous discussion.

Done (after doing additional debugging):
http://bugzilla.kernel.org/show_bug.cgi?id=13389

Marked as regression and set as blocking for #13070.

Cheers,
FJP

Re: 2.6.30-rc6: Reported regressions from 2.6.29

[Rafael J. Wysocki]

On Tuesday 26 May 2009, Frans Pop wrote:
> On Tuesday 26 May 2009, Rafael J. Wysocki wrote:
> > On Monday 25 May 2009, Frans Pop wrote:
> > > Rafael J. Wysocki wrote:
> > > > If you know of any other unresolved regressions from 2.6.29, please
> > > > let me know either and I'll add them to the list.
> > >
> > > It may be worth tracking a possible regression introduced with -rc6
> > > as a result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.
> > >
> > > A new warning that was added in drivers/acpi/processor_throttling.c
> > > (commit 4973b22a: 'ACPI processor: reset the throttling state once
> > > it's invalid') may be triggering in cases where it shouldn't. It
> > > seems to trigger during boot and on 'cat
> > > /proc/acpi/processor/*/throttling'. Otherwise it's probably
> > > relatively harmless.
> > >
> > > See the comments starting at #23 for details.
> >
> > Hmm.  It's really better if you file a separate bug for that with a
> > reference to the previous discussion.
> 
> Done (after doing additional debugging):
> http://bugzilla.kernel.org/show_bug.cgi?id=13389
> 
> Marked as regression and set as blocking for #13070.

Thanks!

Best,
Rafael

Re: [Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

On Sunday 26 April 2009, Justin Madru wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.29.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> > Subject		: horizontal strips of the screen frozen
> > Submitter	: Justin Madru <jdm64@gawab.com>
> > Date		: 2009-04-24 20:59 (2 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> > References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
> >
> >
> >
> >   
> Please mark bug #13187 as a dup of this bug.

Done.

> I sent two separate emails because nobody replied to the first one.
> Sorry for the duplication.

No problem, thanks for the update.

Rafael

Re: [Bug #13188] horizontal strips of the screen frozen

[Justin Madru]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> Subject		: horizontal strips of the screen frozen
> Submitter	: Justin Madru <jdm64@gawab.com>
> Date		: 2009-04-24 20:59 (2 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
>
>
>
>   
Please mark bug #13187 as a dup of this bug.
I sent two separate emails because nobody replied to the first one.
Sorry for the duplication.

Justin Madru

Re: [Bug #13188] horizontal strips of the screen frozen

[Justin Madru]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.29.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
> Subject		: horizontal strips of the screen frozen
> Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-04-24 20:59 (2 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
> References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4
>
>
>
>   
Please mark bug #13187 as a dup of this bug.
I sent two separate emails because nobody replied to the first one.
Sorry for the duplication.

Justin Madru

[Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
Subject		: horizontal strips of the screen frozen
Submitter	: Justin Madru <jdm64@gawab.com>
Date		: 2009-04-24 20:59 (2 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4

[Bug #13188] horizontal strips of the screen frozen

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13188
Subject		: horizontal strips of the screen frozen
Submitter	: Justin Madru <jdm64-u1xxEuL7cY4AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-24 20:59 (2 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=280b713b5b0fd84cf2469098aee88acbb5de859c
References	: http://marc.info/?l=linux-kernel&m=124060685315937&w=4