2.6.36-rc5-git7: Reported regressions from 2.6.35

2.6.36-rc5-git7: Reported regressions from 2.6.35

[Rafael J. Wysocki]

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

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

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


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2010-09-26       46       15          13
  2010-09-20       38       15          15
  2010-09-12       28       14          13
  2010-08-30       21       16          15


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19082
Subject		: fs/fs-writeback.c to dump
Submitter	: Pavel Vasilyev <pavel@pavlinux.ru>
Date		: 2010-09-25 15:52 (2 days old)
Message-ID	: <201009251952.58749.pavel@pavlinux.ru>
References	: http://marc.info/?l=linux-kernel&m=128543035026659&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19072
Subject		: [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2010-09-23 17:02 (4 days old)
Message-ID	: <19611.34846.813757.309183@pilspetsen.it.uu.se>
References	: http://marc.info/?l=linux-kernel&m=128526136531048&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
Subject		: Dirtiable inode bdi default != sb bdi btrfs
Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
Date		: 2010-09-23 0:54 (4 days old)
Message-ID	: <4C9AA546.6050201@cesarb.net>
References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19052
Subject		: 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-09-22 23:47 (5 days old)
Message-ID	: <AANLkTikWQjUQjFJU9MO1+XbSLAEE-GARz+S+Dz2Fgu4h@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128519926626322&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19002
Subject		: Radeon rv730 AGP/KMS/DRM kernel lockup
Submitter	: Duncan <1i5t5.duncan@cox.net>
Date		: 2010-09-23 16:48 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18992
Subject		: warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5
Submitter	: rocko <rockorequin@hotmail.com>
Date		: 2010-09-23 03:07 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18342
Subject		: [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1
Submitter	: Woody Suwalski <terraluna977@gmail.com>
Date		: 2010-09-08 15:10 (19 days old)
Message-ID	: <AANLkTim2mrVRCKg-2couMTFV7krHQp0+2e_cbaiT_KYW@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128395866331382&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17722
Subject		: 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-08-31 20:14 (27 days old)
Message-ID	: <201008312214.52473.thomas@m3y3r.de>
References	: http://marc.info/?l=linux-kernel&m=128328580504227&w=2
		  http://www.spinics.net/lists/netdev/msg140769.html


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17361
Subject		: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2010-08-29 19:59 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17121
Subject		: Two blank rectangles more than 10 cm long when booting
Submitter	: Eric Valette <eric.valette@free.fr>
Date		: 2010-08-26 17:24 (32 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17061
Subject		: 2.6.36-rc1 on zaurus: bluetooth regression
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-08-21 15:24 (37 days old)
Message-ID	: <20100821152445.GA1536@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=128240433828087&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16971
Subject		: qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
Submitter	: Meelis Roos <mroos@linux.ee>
Date		: 2010-08-19 21:03 (39 days old)
Message-ID	: <alpine.SOC.1.00.1008192359310.19654@math.ut.ee>
References	: http://marc.info/?l=linux-kernel&m=128225184900892&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16951
Subject		: hackbench regression with 2.6.36-rc1
Submitter	: Zhang, Yanmin <yanmin_zhang@linux.intel.com>
Date		: 2010-08-18 6:18 (40 days old)
Message-ID	: <1282112318.21202.8.camel@ymzhang.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=128211235904910&w=2


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18962
Subject		: screen failes in kde
Submitter	: Hans de Bruin <jmdebruin@xmsnet.nl>
Date		: 2010-09-22 15:42 (5 days old)
First-Bad-Commit: http://git.kernel.org/linus/e259befd9013e212648c3bd4f6f1fbf92d0dd51d
Handled-By	: Chris Wilson <chris@chris-wilson.co.uk>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31042


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18742
Subject		: PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop
Submitter	: infernix <infernix@infernix.net>
Date		: 2010-09-15 14:35 (12 days old)
Message-ID	: <4C90D998.6050103@infernix.net>
References	: http://marc.info/?l=linux-kernel&m=128456187928496&w=2
Handled-By	: Jesse Barnes <jbarnes@virtuousgeek.org>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31112


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

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

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

Thanks!

[Bug #16951] hackbench regression with 2.6.36-rc1

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16951
Subject		: hackbench regression with 2.6.36-rc1
Submitter	: Zhang, Yanmin <yanmin_zhang@linux.intel.com>
Date		: 2010-08-18 6:18 (40 days old)
Message-ID	: <1282112318.21202.8.camel@ymzhang.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=128211235904910&w=2

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17361
Subject		: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2010-08-29 19:59 (29 days old)

[Bug #17061] 2.6.36-rc1 on zaurus: bluetooth regression

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17061
Subject		: 2.6.36-rc1 on zaurus: bluetooth regression
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2010-08-21 15:24 (37 days old)
Message-ID	: <20100821152445.GA1536@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=128240433828087&w=2

[Bug #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16971
Subject		: qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
Submitter	: Meelis Roos <mroos@linux.ee>
Date		: 2010-08-19 21:03 (39 days old)
Message-ID	: <alpine.SOC.1.00.1008192359310.19654@math.ut.ee>
References	: http://marc.info/?l=linux-kernel&m=128225184900892&w=2

[Bug #17121] Two blank rectangles more than 10 cm long when booting

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17121
Subject		: Two blank rectangles more than 10 cm long when booting
Submitter	: Eric Valette <eric.valette@free.fr>
Date		: 2010-08-26 17:24 (32 days old)

[Bug #17722] 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17722
Subject		: 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed
Submitter	: Thomas Meyer <thomas@m3y3r.de>
Date		: 2010-08-31 20:14 (27 days old)
Message-ID	: <201008312214.52473.thomas@m3y3r.de>
References	: http://marc.info/?l=linux-kernel&m=128328580504227&w=2
		  http://www.spinics.net/lists/netdev/msg140769.html

[Bug #18342] [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18342
Subject		: [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1
Submitter	: Woody Suwalski <terraluna977@gmail.com>
Date		: 2010-09-08 15:10 (19 days old)
Message-ID	: <AANLkTim2mrVRCKg-2couMTFV7krHQp0+2e_cbaiT_KYW@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128395866331382&w=2

[Bug #18742] PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18742
Subject		: PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop
Submitter	: infernix <infernix@infernix.net>
Date		: 2010-09-15 14:35 (12 days old)
Message-ID	: <4C90D998.6050103@infernix.net>
References	: http://marc.info/?l=linux-kernel&m=128456187928496&w=2
Handled-By	: Jesse Barnes <jbarnes@virtuousgeek.org>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31112

[Bug #18962] screen failes in kde

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18962
Subject		: screen failes in kde
Submitter	: Hans de Bruin <jmdebruin@xmsnet.nl>
Date		: 2010-09-22 15:42 (5 days old)
First-Bad-Commit: http://git.kernel.org/linus/e259befd9013e212648c3bd4f6f1fbf92d0dd51d
Handled-By	: Chris Wilson <chris@chris-wilson.co.uk>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31042

[Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
Subject		: Dirtiable inode bdi default != sb bdi btrfs
Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
Date		: 2010-09-23 0:54 (4 days old)
Message-ID	: <4C9AA546.6050201@cesarb.net>
References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2

[Bug #19002] Radeon rv730 AGP/KMS/DRM kernel lockup

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19002
Subject		: Radeon rv730 AGP/KMS/DRM kernel lockup
Submitter	: Duncan <1i5t5.duncan@cox.net>
Date		: 2010-09-23 16:48 (4 days old)

[Bug #19052] 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19052
Subject		: 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-09-22 23:47 (5 days old)
Message-ID	: <AANLkTikWQjUQjFJU9MO1+XbSLAEE-GARz+S+Dz2Fgu4h@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128519926626322&w=2

[Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19072
Subject		: [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2010-09-23 17:02 (4 days old)
Message-ID	: <19611.34846.813757.309183@pilspetsen.it.uu.se>
References	: http://marc.info/?l=linux-kernel&m=128526136531048&w=2

[Bug #18992] warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18992
Subject		: warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5
Submitter	: rocko <rockorequin@hotmail.com>
Date		: 2010-09-23 03:07 (4 days old)

[Bug #19082] fs/fs-writeback.c to dump

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19082
Subject		: fs/fs-writeback.c to dump
Submitter	: Pavel Vasilyev <pavel@pavlinux.ru>
Date		: 2010-09-25 15:52 (2 days old)
Message-ID	: <201009251952.58749.pavel@pavlinux.ru>
References	: http://marc.info/?l=linux-kernel&m=128543035026659&w=2

Re: [Bug #19082] fs/fs-writeback.c to dump

[Pavel Vasilyev]

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

В сообщении от Понедельник 27 сентября 2010 00:04:16 вы написали:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the
> tracking team know (either way).

I don't know, this bug or not :)

# view +73 fs/fs-writeback.c
...

static inline struct backing_dev_info *inode_to_bdi(struct inode *inode)
{
        struct super_block *sb = inode->i_sb;
        struct backing_dev_info *bdi = inode->i_mapping->backing_dev_info;

        /*
         * For inodes on standard filesystems, we use superblock's bdi. For
         * inodes on virtual filesystems, we want to use inode mapping's bdi
         * because they can possibly point to something useful (think about
         * block_dev filesystem).
         */

        if (sb->s_bdi && sb->s_bdi != &noop_backing_dev_info) {

               /* Some device inodes could play dirty tricks. Catch them... */

          WARN(bdi != sb->s_bdi && bdi_cap_writeback_dirty(bdi),
                        "Dirtiable inode bdi %s != sb bdi %s\n",
                        bdi->name, sb->s_bdi->name);
                return sb->s_bdi;
        }
        return bdi;
}




> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19082
> Subject		: fs/fs-writeback.c to dump
> Submitter	: Pavel Vasilyev <pavel@pavlinux.ru>
> Date		: 2010-09-25 15:52 (2 days old)
> Message-ID	: <201009251952.58749.pavel@pavlinux.ru>
> References	: http://marc.info/?l=linux-kernel&m=128543035026659&w=2

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

Re: [Bug #17121] Two blank rectangles more than 10 cm long when booting

[Eric Valette]

On 26/09/2010 22:04, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the tracking team
> know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17121
> Subject		: Two blank rectangles more than 10 cm long when booting
> Submitter	: Eric Valette<eric.valette@free.fr>
> Date		: 2010-08-26 17:24 (32 days old)
>
>

Still present on 2.6.36-rc5-git7.

--eric

Re: [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP

[Mikael Pettersson]

Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=3D19072
> Subject	: [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
> Submitter	: Mikael Pettersson <mikpe@it.uu.se>
> Date		: 2010-09-23 17:02 (4 days old)
> Message-ID	: <19611.34846.813757.309183@pilspetsen.it.uu.se>
> References	: http://marc.info/?l=3Dlinux-kernel&m=3D128526136531048&w=3D2

Still present in 2.6.36-rc5.

Re: [Bug #17121] Two blank rectangles more than 10 cm long when booting

[Rafael J. Wysocki]

On Monday, September 27, 2010, Eric Valette wrote:
> On 26/09/2010 22:04, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.35.  Please verify if it still should be listed and let the tracking team
> > know (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17121
> > Subject		: Two blank rectangles more than 10 cm long when booting
> > Submitter	: Eric Valette<eric.valette@free.fr>
> > Date		: 2010-08-26 17:24 (32 days old)
> >
> >
> 
> Still present on 2.6.36-rc5-git7.

Thanks for the update.

Rafael

Re: [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP

[Rafael J. Wysocki]

On Monday, September 27, 2010, Mikael Pettersson wrote:
> Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.35.  Please verify if it still should be listed and let the tracking team
> > know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=3D19072
> > Subject	: [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
> > Submitter	: Mikael Pettersson <mikpe@it.uu.se>
> > Date		: 2010-09-23 17:02 (4 days old)
> > Message-ID	: <19611.34846.813757.309183@pilspetsen.it.uu.se>
> > References	: http://marc.info/?l=3Dlinux-kernel&m=3D128526136531048&w=3D2
> 
> Still present in 2.6.36-rc5.

Thanks for the update.

Rafael

Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Ted Ts'o]

On Sun, Sep 26, 2010 at 10:04:13PM +0200, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17361
> Subject		: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
> Submitter	: Christian Casteyde <casteyde.christian@free.fr>
> Date		: 2010-08-29 19:59 (29 days old)

See my latest comment here:

    https://bugzilla.kernel.org/show_bug.cgi?id=17361#c14

This subject line is highly misleading, since after -rc4, the stack
traces are in places all over the kernel, in other places other than
ext4/jbd2.  So I fear no one is looking at this bug report given the
highly misleading subject line.

It looks like you have spinlock debugging, and yet there wan't any
spinlocks listed on the initial ext4 might_sleep() warning.  So
something looks highly confused.

The fact that you closed other bugs as duplicates of this one that
relate to kmemcheck makes me wonder if this is really a kmemcheck bug.
(If so, the subject line here is doubly, doubly misleading.)

Do you see any symptoms if you turn off kmemcheck?  Are you sure this
isn't just only a kmemcheck bug?

					- Ted

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Ted Ts'o]

On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
> Subject		: Dirtiable inode bdi default != sb bdi btrfs
> Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
> Date		: 2010-09-23 0:54 (4 days old)
> Message-ID	: <4C9AA546.6050201@cesarb.net>
> References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2

Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
systems.  So I'm seeing this as a known regression from rc3 to rc6.
Maybe it's different bug with ext4, but in any case, it's highly
annoying.

						- Ted

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Rafael J. Wysocki]

On Saturday, October 02, 2010, Ted Ts'o wrote:
> On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.35.  Please verify if it still should be listed and let the tracking team
> > know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
> > Subject		: Dirtiable inode bdi default != sb bdi btrfs
> > Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
> > Date		: 2010-09-23 0:54 (4 days old)
> > Message-ID	: <4C9AA546.6050201@cesarb.net>
> > References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2
> 
> Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
> when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
> partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
> systems.  So I'm seeing this as a known regression from rc3 to rc6.
> Maybe it's different bug with ext4, but in any case, it's highly
> annoying.

Thanks for the info.  I wonder who should see this report.

Andrew, do you know whose area that is?

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Ted Ts'o]

On Sat, Oct 02, 2010 at 11:58:35PM +0200, Rafael J. Wysocki wrote:
> On Saturday, October 02, 2010, Ted Ts'o wrote:
> > On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.35.  Please verify if it still should be listed and let the tracking team
> > > know (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
> > > Subject		: Dirtiable inode bdi default != sb bdi btrfs
> > > Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
> > > Date		: 2010-09-23 0:54 (4 days old)
> > > Message-ID	: <4C9AA546.6050201@cesarb.net>
> > > References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2
> > 
> > Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
> > when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
> > partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
> > systems.  So I'm seeing this as a known regression from rc3 to rc6.
> > Maybe it's different bug with ext4, but in any case, it's highly
> > annoying.
> 
> Thanks for the info.  I wonder who should see this report.

Oops, correction, the correct warning that I'm seeing is:

Dirtiable inode bdi block != sb bdi block
                    ^^^^^           ^^^^^

------------[ cut here ]------------
WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 inode_to_bdi+0x4e/0x5c()
Hardware name: 
Dirtiable inode bdi block != sb bdi block
Modules linked in:
Pid: 21649, comm: mkfs.ext4 Tainted: G        W   2.6.36-rc6-00016-gcc25699 #735
Call Trace:
 [<c015a2e2>] warn_slowpath_common+0x6a/0x7f
 [<c020a762>] ? inode_to_bdi+0x4e/0x5c
 [<c015a36a>] warn_slowpath_fmt+0x2b/0x2f
 [<c020a762>] inode_to_bdi+0x4e/0x5c
 [<c020b6c3>] __mark_inode_dirty+0xaf/0x162
 [<c0202305>] file_update_time+0xcc/0xe9
 [<c01c68dd>] __generic_file_aio_write+0x136/0x28f
 [<c02145a4>] blkdev_aio_write+0x33/0x72
 [<c01f20da>] do_sync_write+0x8f/0xca
 [<c0647678>] ? mutex_unlock+0xd/0xf
 [<c030d528>] ? security_file_permission+0x27/0x2b
 [<c01f227c>] ? rw_verify_area+0x9d/0xc0
 [<c01f204b>] ? do_sync_write+0x0/0xca
 [<c01f2629>] vfs_write+0x85/0xe3
 [<c01f2725>] sys_write+0x40/0x62
 [<c064915d>] syscall_call+0x7/0xb
---[ end trace 1f39401760ab3a42 ]---

					- Ted

Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Vegard Nossum]

On 2 October 2010 18:52, Ted Ts'o <tytso@mit.edu> wrote:
> On Sun, Sep 26, 2010 at 10:04:13PM +0200, Rafael J. Wysocki wrote:
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=17361
>> Subject               : Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
>> Submitter     : Christian Casteyde <casteyde.christian@free.fr>
>> Date          : 2010-08-29 19:59 (29 days old)
>
> See my latest comment here:
>
>    https://bugzilla.kernel.org/show_bug.cgi?id=17361#c14
>
> This subject line is highly misleading, since after -rc4, the stack
> traces are in places all over the kernel, in other places other than
> ext4/jbd2.  So I fear no one is looking at this bug report given the
> highly misleading subject line.
>
> It looks like you have spinlock debugging, and yet there wan't any
> spinlocks listed on the initial ext4 might_sleep() warning.  So
> something looks highly confused.
>
> The fact that you closed other bugs as duplicates of this one that
> relate to kmemcheck makes me wonder if this is really a kmemcheck bug.
> (If so, the subject line here is doubly, doubly misleading.)
>
> Do you see any symptoms if you turn off kmemcheck?  Are you sure this
> isn't just only a kmemcheck bug?

I just had a quick glance at the report, and here's my gut feeling: I
see perf symbols in the stack trace. I don't think kmemcheck and perf
play nicely together (for example if perf uses NMIs to write data to
its buffers, it could get a page fault inside the NMI handler, which
is not so nice, I think).

Isn't this exactly what Frederic Weisbecker tried to detect and warn
about in a patch that I saw recently?

Please do as Ted suggested and try to turn kmemcheck off.


Vegard

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Tejun Heo]

(cc'in Jan and quoting the whole body for him)

Jan, any chance this is caused by the recent bdi change?

On 10/03/2010 04:27 AM, Ted Ts'o wrote:
> On Sat, Oct 02, 2010 at 11:58:35PM +0200, Rafael J. Wysocki wrote:
>> On Saturday, October 02, 2010, Ted Ts'o wrote:
>>> On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
>>>> The following bug entry is on the current list of known regressions
>>>> from 2.6.35.  Please verify if it still should be listed and let the tracking team
>>>> know (either way).
>>>>
>>>>
>>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
>>>> Subject		: Dirtiable inode bdi default != sb bdi btrfs
>>>> Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
>>>> Date		: 2010-09-23 0:54 (4 days old)
>>>> Message-ID	: <4C9AA546.6050201@cesarb.net>
>>>> References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2
>>>
>>> Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
>>> when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
>>> partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
>>> systems.  So I'm seeing this as a known regression from rc3 to rc6.
>>> Maybe it's different bug with ext4, but in any case, it's highly
>>> annoying.
>>
>> Thanks for the info.  I wonder who should see this report.
> 
> Oops, correction, the correct warning that I'm seeing is:
> 
> Dirtiable inode bdi block != sb bdi block
>                     ^^^^^           ^^^^^
> 
> ------------[ cut here ]------------
> WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 inode_to_bdi+0x4e/0x5c()
> Hardware name: 
> Dirtiable inode bdi block != sb bdi block
> Modules linked in:
> Pid: 21649, comm: mkfs.ext4 Tainted: G        W   2.6.36-rc6-00016-gcc25699 #735
> Call Trace:
>  [<c015a2e2>] warn_slowpath_common+0x6a/0x7f
>  [<c020a762>] ? inode_to_bdi+0x4e/0x5c
>  [<c015a36a>] warn_slowpath_fmt+0x2b/0x2f
>  [<c020a762>] inode_to_bdi+0x4e/0x5c
>  [<c020b6c3>] __mark_inode_dirty+0xaf/0x162
>  [<c0202305>] file_update_time+0xcc/0xe9
>  [<c01c68dd>] __generic_file_aio_write+0x136/0x28f
>  [<c02145a4>] blkdev_aio_write+0x33/0x72
>  [<c01f20da>] do_sync_write+0x8f/0xca
>  [<c0647678>] ? mutex_unlock+0xd/0xf
>  [<c030d528>] ? security_file_permission+0x27/0x2b
>  [<c01f227c>] ? rw_verify_area+0x9d/0xc0
>  [<c01f204b>] ? do_sync_write+0x0/0xca
>  [<c01f2629>] vfs_write+0x85/0xe3
>  [<c01f2725>] sys_write+0x40/0x62
>  [<c064915d>] syscall_call+0x7/0xb
> ---[ end trace 1f39401760ab3a42 ]---

-- 
tejun

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Jan Kara]

On Sun 03-10-10 17:16:51, Tejun Heo wrote:
> On 10/03/2010 04:27 AM, Ted Ts'o wrote:
> > WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 inode_to_bdi+0x4e/0x5c()
> > Hardware name: 
> > Dirtiable inode bdi block != sb bdi block
> > Modules linked in:
> > Pid: 21649, comm: mkfs.ext4 Tainted: G        W   2.6.36-rc6-00016-gcc25699 #735
> > Call Trace:
> >  [<c015a2e2>] warn_slowpath_common+0x6a/0x7f
> >  [<c020a762>] ? inode_to_bdi+0x4e/0x5c
> >  [<c015a36a>] warn_slowpath_fmt+0x2b/0x2f
> >  [<c020a762>] inode_to_bdi+0x4e/0x5c
> >  [<c020b6c3>] __mark_inode_dirty+0xaf/0x162
> >  [<c0202305>] file_update_time+0xcc/0xe9
> >  [<c01c68dd>] __generic_file_aio_write+0x136/0x28f
> >  [<c02145a4>] blkdev_aio_write+0x33/0x72
> >  [<c01f20da>] do_sync_write+0x8f/0xca
> >  [<c0647678>] ? mutex_unlock+0xd/0xf
> >  [<c030d528>] ? security_file_permission+0x27/0x2b
> >  [<c01f227c>] ? rw_verify_area+0x9d/0xc0
> >  [<c01f204b>] ? do_sync_write+0x0/0xca
> >  [<c01f2629>] vfs_write+0x85/0xe3
> >  [<c01f2725>] sys_write+0x40/0x62
> >  [<c064915d>] syscall_call+0x7/0xb
> > ---[ end trace 1f39401760ab3a42 ]---
  Yes, it's caused by one of my fixes. It's harmless (the warning I've
added is just too strict). Christoph has a patch that also fixes this
- http://lkml.org/lkml/2010/9/29/76. I hope he'll push it soon.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Christoph Hellwig]

On Mon, Oct 04, 2010 at 11:59:44AM +0200, Jan Kara wrote:
>   Yes, it's caused by one of my fixes. It's harmless (the warning I've
> added is just too strict). Christoph has a patch that also fixes this
> - http://lkml.org/lkml/2010/9/29/76. I hope he'll push it soon.

Jens is the writeback maintainer, so he will have to pick it up.

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Jens Axboe]

On 2010-10-04 12:12, Christoph Hellwig wrote:
> On Mon, Oct 04, 2010 at 11:59:44AM +0200, Jan Kara wrote:
>>   Yes, it's caused by one of my fixes. It's harmless (the warning I've
>> added is just too strict). Christoph has a patch that also fixes this
>> - http://lkml.org/lkml/2010/9/29/76. I hope he'll push it soon.
> 
> Jens is the writeback maintainer, so he will have to pick it up.

It's in, will push it asap.

-- 
Jens Axboe

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Andrew Morton]

On Sat, 2 Oct 2010 23:58:35 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Saturday, October 02, 2010, Ted Ts'o wrote:
> > On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.35.  Please verify if it still should be listed and let the tracking team
> > > know (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
> > > Subject		: Dirtiable inode bdi default != sb bdi btrfs
> > > Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
> > > Date		: 2010-09-23 0:54 (4 days old)
> > > Message-ID	: <4C9AA546.6050201@cesarb.net>
> > > References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2
> > 
> > Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
> > when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
> > partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
> > systems.  So I'm seeing this as a known regression from rc3 to rc6.
> > Maybe it's different bug with ext4, but in any case, it's highly
> > annoying.
> 
> Thanks for the info.  I wonder who should see this report.
> 
> Andrew, do you know whose area that is?

Christoph had a patch, and Jan had another patch.  Maybe

commit 692ebd17c2905313fff3c504c249c6a0faad16ec
Author: Jan Kara <jack@suse.cz>
Date:   Tue Sep 21 11:51:01 2010 +0200

    bdi: Fix warnings in __mark_inode_dirty for /dev/zero and friends

already fixed this?

Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Ted Ts'o]

On Mon, Oct 04, 2010 at 01:09:11PM -0700, Andrew Morton wrote:
> 
> Christoph had a patch, and Jan had another patch.  Maybe
> 
> commit 692ebd17c2905313fff3c504c249c6a0faad16ec
> Author: Jan Kara <jack@suse.cz>
> Date:   Tue Sep 21 11:51:01 2010 +0200
> 
>     bdi: Fix warnings in __mark_inode_dirty for /dev/zero and friends
> 
> already fixed this?
> 

Actually, I do believe that's the _cause_ of what I was seeing.  The
fix is:

	  http://lkml.org/lkml/2010/9/29/76

						- Ted


				

[Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
Subject		: Dirtiable inode bdi default != sb bdi btrfs
Submitter	: Cesar Eduardo Barros <cesarb@cesarb.net>
Date		: 2010-09-23 0:54 (11 days old)
Message-ID	: <<4C9AA546.6050201@cesarb.net>>
References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2