2.6.36-rc6-git2: Reported regressions from 2.6.35

2.6.36-rc6-git2: 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-10-03       52       16          14
  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=19642
Subject		: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
Submitter	: George Spelvin <linux@horizon.com>
Date		: 2010-09-30 21:10 (4 days old)
Message-ID	: <20100930211006.27449.qmail@science.horizon.com>
References	: http://marc.info/?l=linux-kernel&m=128588102620299&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19632
Subject		: 2.6.36-rc6: modprobe Not tainted warning
Submitter	: Heinz Diehl <htd@fritha.org>
Date		: 2010-09-30 18:25 (4 days old)
Message-ID	: <20100930182516.GA15089@fritha.org>
References	: http://marc.info/?l=linux-kernel&m=128587114004680&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19392
Subject		: WARNING: at drivers/net/wireless/ath/ath5k/base.c:3475 ath5k_bss_info_changed+0x44/0x168 [ath5k]()
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2010-09-28 22:30 (6 days old)
Message-ID	: <AANLkTim5WCGKPvEkOkO_YnMF9pg8mvLfQoFBNUFpfa_k@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128571307018635&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19372
Subject		: 2.6.36-rc6: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x35a/0x3c0
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2010-09-29 21:29 (5 days old)
Message-ID	: <20100929212923.GA5578@core2.telecom.by>
References	: http://marc.info/?l=linux-kernel&m=128579579400315&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19142
Subject		: Screen flickers when switching from the console to X
Submitter	: Andrey Rahmatullin <wrar@altlinux.org>
Date		: 2010-09-27 12:05 (7 days old)


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 (11 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 (11 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 (12 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 (11 days old)


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 (36 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 (39 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 (44 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 (46 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 (47 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=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 (19 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-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 (34 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
Handled-By	: Florian Mickler <florian@mickler.org>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31671


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!

2.6.36-rc6-git2: 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-10-03       52       16          14
  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=19642
Subject		: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
Submitter	: George Spelvin <linux@horizon.com>
Date		: 2010-09-30 21:10 (4 days old)
Message-ID	: <20100930211006.27449.qmail@science.horizon.com>
References	: http://marc.info/?l=linux-kernel&m=128588102620299&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19632
Subject		: 2.6.36-rc6: modprobe Not tainted warning
Submitter	: Heinz Diehl <htd@fritha.org>
Date		: 2010-09-30 18:25 (4 days old)
Message-ID	: <20100930182516.GA15089@fritha.org>
References	: http://marc.info/?l=linux-kernel&m=128587114004680&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19392
Subject		: WARNING: at drivers/net/wireless/ath/ath5k/base.c:3475 ath5k_bss_info_changed+0x44/0x168 [ath5k]()
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2010-09-28 22:30 (6 days old)
Message-ID	: <AANLkTim5WCGKPvEkOkO_YnMF9pg8mvLfQoFBNUFpfa_k@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128571307018635&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19372
Subject		: 2.6.36-rc6: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x35a/0x3c0
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2010-09-29 21:29 (5 days old)
Message-ID	: <20100929212923.GA5578@core2.telecom.by>
References	: http://marc.info/?l=linux-kernel&m=128579579400315&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19142
Subject		: Screen flickers when switching from the console to X
Submitter	: Andrey Rahmatullin <wrar@altlinux.org>
Date		: 2010-09-27 12:05 (7 days old)


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 (11 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 (11 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 (12 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 (11 days old)


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 (36 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 (39 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 (44 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 (46 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 (47 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=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 (19 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-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 (34 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
Handled-By	: Florian Mickler <florian@mickler.org>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31671


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-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Date		: 2010-08-18 6:18 (47 days old)
Message-ID	: <1282112318.21202.8.camel-sz7BYL/Y5Hu/P+R7jlPCFVaTQe2KTcn/@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128211235904910&w=2

[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 (47 days old)
Message-ID	: <1282112318.21202.8.camel@ymzhang.sh.intel.com>
References	: http://marc.info/?l=linux-kernel&m=128211235904910&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-ZHiucA87ovfk1uMJSBkQmQ@public.gmane.org>
Date		: 2010-09-15 14:35 (19 days old)
Message-ID	: <4C90D998.6050103-ZHiucA87ovfk1uMJSBkQmQ@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128456187928496&w=2
Handled-By	: Jesse Barnes <jbarnes-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31112

[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 (19 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 #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 (44 days old)
Message-ID	: <20100821152445.GA1536@ucw.cz>
References	: http://marc.info/?l=linux-kernel&m=128240433828087&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-GANU6spQydw@public.gmane.org>
Date		: 2010-08-26 17:24 (39 days old)

[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 (39 days old)

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

[Eric Valette]

On 03/10/2010 23:19, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.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-GANU6spQydw@public.gmane.org>
> Date		: 2010-08-26 17:24 (39 days old)
>
>


2.6.36-rc6-git2 ! still there.

--eric

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

[Eric Valette]

On 03/10/2010 23:19, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.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 (39 days old)
>
>


2.6.36-rc6-git2 ! still there.

--eric

[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-Y27EyoLml9s@public.gmane.org>
Date		: 2010-08-19 21:03 (46 days old)
Message-ID	: <alpine.SOC.1.00.1008192359310.19654-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128225184900892&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 (46 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 #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 (34 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
Handled-By	: Florian Mickler <florian@mickler.org>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31671

[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 (36 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 (12 days old)
Message-ID	: <AANLkTikWQjUQjFJU9MO1+XbSLAEE-GARz+S+Dz2Fgu4h@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128519926626322&w=2

[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

[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 (11 days old)

[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-1zs4UD6AkMk@public.gmane.org>
Date		: 2010-09-23 17:02 (11 days old)
Message-ID	: <19611.34846.813757.309183-tgku4HJDRZih8lFjZTKsyTAV6s6igYVG@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128526136531048&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 (11 days old)
Message-ID	: <19611.34846.813757.309183@pilspetsen.it.uu.se>
References	: http://marc.info/?l=linux-kernel&m=128526136531048&w=2

[Bug #19392] WARNING: at drivers/net/wireless/ath/ath5k/base.c:3475 ath5k_bss_info_changed+0x44/0x168 [ath5k]()

[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=19392
Subject		: WARNING: at drivers/net/wireless/ath/ath5k/base.c:3475 ath5k_bss_info_changed+0x44/0x168 [ath5k]()
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2010-09-28 22:30 (6 days old)
Message-ID	: <AANLkTim5WCGKPvEkOkO_YnMF9pg8mvLfQoFBNUFpfa_k@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=128571307018635&w=2

[Bug #19142] Screen flickers when switching from the console to X

[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=19142
Subject		: Screen flickers when switching from the console to X
Submitter	: Andrey Rahmatullin <wrar@altlinux.org>
Date		: 2010-09-27 12:05 (7 days old)

[Bug #19372] 2.6.36-rc6: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x35a/0x3c0

[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=19372
Subject		: 2.6.36-rc6: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x35a/0x3c0
Submitter	: Alexey Dobriyan <adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-09-29 21:29 (5 days old)
Message-ID	: <20100929212923.GA5578-y0M6fkzdUYllgR+Ck+lCww@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128579579400315&w=2

[Bug #19372] 2.6.36-rc6: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x35a/0x3c0

[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=19372
Subject		: 2.6.36-rc6: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x35a/0x3c0
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2010-09-29 21:29 (5 days old)
Message-ID	: <20100929212923.GA5578@core2.telecom.by>
References	: http://marc.info/?l=linux-kernel&m=128579579400315&w=2

[Bug #19632] 2.6.36-rc6: modprobe Not tainted warning

[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=19632
Subject		: 2.6.36-rc6: modprobe Not tainted warning
Submitter	: Heinz Diehl <htd@fritha.org>
Date		: 2010-09-30 18:25 (4 days old)
Message-ID	: <20100930182516.GA15089@fritha.org>
References	: http://marc.info/?l=linux-kernel&m=128587114004680&w=2

Re: [Bug #19632] 2.6.36-rc6: modprobe Not tainted warning

[Heinz Diehl]

On 04.10.2010, 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=19632
> Subject		: 2.6.36-rc6: modprobe Not tainted warning
> Submitter	: Heinz Diehl <htd-iEI8Y0CNJBYdnm+yROfE0A@public.gmane.org>
> Date		: 2010-09-30 18:25 (4 days old)
> Message-ID	: <20100930182516.GA15089-iEI8Y0CNJBYdnm+yROfE0A@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=128587114004680&w=2

This should still be listed, yes. It is also present in the latest rc from
git repository.

Re: [Bug #19632] 2.6.36-rc6: modprobe Not tainted warning

[Heinz Diehl]

On 04.10.2010, 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=19632
> Subject		: 2.6.36-rc6: modprobe Not tainted warning
> Submitter	: Heinz Diehl <htd@fritha.org>
> Date		: 2010-09-30 18:25 (4 days old)
> Message-ID	: <20100930182516.GA15089@fritha.org>
> References	: http://marc.info/?l=linux-kernel&m=128587114004680&w=2

This should still be listed, yes. It is also present in the latest rc from
git repository.

[Bug #19642] 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113

[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=19642
Subject		: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
Submitter	: George Spelvin <linux@horizon.com>
Date		: 2010-09-30 21:10 (4 days old)
Message-ID	: <20100930211006.27449.qmail@science.horizon.com>
References	: http://marc.info/?l=linux-kernel&m=128588102620299&w=2

Re: 2.6.36-rc6-git2: Reported regressions from 2.6.35

[Ben Hutchings]

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

On Sun, 2010-10-03 at 23:15 +0200, Rafael J. Wysocki wrote:
[...]
> 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 (46 days old)
> Message-ID	: <alpine.SOC.1.00.1008192359310.19654@math.ut.ee>
> References	: http://marc.info/?l=linux-kernel&m=128225184900892&w=2
[...]

A patch is available:

http://thread.gmane.org/gmane.linux.scsi/62561

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

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

Re: 2.6.36-rc6-git2: Reported regressions from 2.6.35

[Luis R. Rodriguez]

Below are the 802.11 and Bluetooth ones:

On Sun, Oct 3, 2010 at 2:15 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Unresolved regressions
> ----------------------

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=19392
> Subject         : WARNING: at drivers/net/wireless/ath/ath5k/base.c:3475 ath5k_bss_info_changed+0x44/0x168 [ath5k]()
> Submitter       : Justin Mattock <justinmattock@gmail.com>
> Date            : 2010-09-28 22:30 (6 days old)
> Message-ID      : <AANLkTim5WCGKPvEkOkO_YnMF9pg8mvLfQoFBNUFpfa_k@mail.gmail.com>
> References      : http://marc.info/?l=linux-kernel&m=128571307018635&w=2

WTF -- this ended up in a bisect pointing to some PCMCIA patch! Justin:

  * does this happen with wireless-testing.git ?
  * Did you do the bisect on the entire kernel? What git tree are you
using to bisect?

Did you simply bring up the interface and then suspsend? Did you not
add a new interface in between this? ath5k's add_interace has:

        if (sc->vif) {
                ret = 0;
                goto end;
        }

But why does it just allow this to go through without complaining if
multiple vifs are not supported?


>
> 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 (44 days old)
> Message-ID      : <20100821152445.GA1536@ucw.cz>
> References      : http://marc.info/?l=linux-kernel&m=128240433828087&w=2

I see no updates to this since August. There are boat load of PCMCIA
changes recently, is bisect possible here?


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


> 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 (34 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
> Handled-By      : Florian Mickler <florian@mickler.org>
> Patch           : https://bugzilla.kernel.org/attachment.cgi?id=31671

This seems fixed.

  Luis

Re: 2.6.36-rc6-git2: Reported regressions from 2.6.35

[Dominik Brodowski]

Hey,

On Mon, Oct 04, 2010 at 11:35:25AM -0700, Luis R. Rodriguez wrote:
> > 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 (44 days old)
> > Message-ID      : <20100821152445.GA1536@ucw.cz>
> > References      : http://marc.info/?l=linux-kernel&m=128240433828087&w=2
> 
> I see no updates to this since August. There are boat load of PCMCIA
> changes recently, is bisect possible here?

Pavel already verified the PCMCIA-bigdiff since 2.6.35 does work, so it is
_not_ a PCMCIA issue.

http://www.mail-archive.com/linux-pcmcia@lists.infradead.org/msg03460.html

Best,
	Dominik

Re: 2.6.36-rc6-git2: Reported regressions from 2.6.35

[Justin P. Mattock]

On 10/04/2010 11:35 AM, Luis R. Rodriguez wrote:
> Below are the 802.11 and Bluetooth ones:
>
> On Sun, Oct 3, 2010 at 2:15 PM, Rafael J. Wysocki<rjw@sisk.pl>  wrote:
>> Unresolved regressions
>> ----------------------
>
>> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=19392
>> Subject         : WARNING: at drivers/net/wireless/ath/ath5k/base.c:3475 ath5k_bss_info_changed+0x44/0x168 [ath5k]()
>> Submitter       : Justin Mattock<justinmattock@gmail.com>
>> Date            : 2010-09-28 22:30 (6 days old)
>> Message-ID      :<AANLkTim5WCGKPvEkOkO_YnMF9pg8mvLfQoFBNUFpfa_k@mail.gmail.com>
>> References      : http://marc.info/?l=linux-kernel&m=128571307018635&w=2
>
> WTF -- this ended up in a bisect pointing to some PCMCIA patch! Justin:
>
>    * does this happen with wireless-testing.git ?

no this is the current Linus tree(have not tried any other tree).
as for the unresolved regression, this just was filed a few days ago..

>    * Did you do the bisect on the entire kernel? What git tree are you
> using to bisect?
>

the bisect had to be between 2.6.34 and 2.6.32 due to pcmcia breaking 
after 2.6.34(there is a bug report for that, but got resolved)

> Did you simply bring up the interface and then suspsend? Did you not
> add a new interface in between this? ath5k's add_interace has:
>
>          if (sc->vif) {
>                  ret = 0;
>                  goto end;
>          }
>
> But why does it just allow this to go through without complaining if
> multiple vifs are not supported?
>
>

the system is opensuse 11.2, I just simply start the machine boot up,
after nm connects I open a terminal then suspend in the terminal, upon 
wakeup this message appears.

>>
>> 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 (44 days old)
>> Message-ID      :<20100821152445.GA1536@ucw.cz>
>> References      : http://marc.info/?l=linux-kernel&m=128240433828087&w=2
>
> I see no updates to this since August. There are boat load of PCMCIA
> changes recently, is bisect possible here?
>
>

yeah the first pcmcia bug I hit with this machine was back in may/june 
ended up doing a bisect for that(which was painful due to a slow 
machine)which ended up getting fixed.(never thought to check s2ram after 
that)

as for bluetooth the only issue I have with that is for my other 
machines which is hitting this: http://lkml.org/lkml/2010/9/1/61
(but have not had a chance to follow through due to doing the update 
broken web addresses in the kernel)

>> Regressions with patches
>> ------------------------
>
>
>> 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 (34 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
>> Handled-By      : Florian Mickler<florian@mickler.org>
>> Patch           : https://bugzilla.kernel.org/attachment.cgi?id=31671
>
> This seems fixed.
>
>    Luis
>

alright if this is with the latest wireless tree, then I can throw that 
in to verify that it is indeed fixed..

Justin P. Mattock

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-wkUsHEiXLHUox3rIn2DAYQ@public.gmane.org>
Date		: 2010-09-25 15:52 (2 days old)
Message-ID	: <201009251952.58749.pavel-wkUsHEiXLHUox3rIn2DAYQ@public.gmane.org>
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-1zs4UD6AkMk@public.gmane.org>
Date		: 2010-09-23 17:02 (4 days old)
Message-ID	: <19611.34846.813757.309183-tgku4HJDRZih8lFjZTKsyTAV6s6igYVG@public.gmane.org>
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-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
Date		: 2010-09-23 0:54 (4 days old)
Message-ID	: <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-09-22 23:47 (5 days old)
Message-ID	: <AANLkTikWQjUQjFJU9MO1+XbSLAEE-GARz+S+Dz2Fgu4h-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-j9pdmedNgrk@public.gmane.org>
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-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-09-08 15:10 (19 days old)
Message-ID	: <AANLkTim2mrVRCKg-2couMTFV7krHQp0+2e_cbaiT_KYW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-VsYtu1Qij5c@public.gmane.org>
Date		: 2010-08-31 20:14 (27 days old)
Message-ID	: <201008312214.52473.thomas-VsYtu1Qij5c@public.gmane.org>
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-GANU6spQydw@public.gmane.org>
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-GANU6spQydw@public.gmane.org>
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-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-08-21 15:24 (37 days old)
Message-ID	: <20100821152445.GA1536-+ZI9xUNit7I@public.gmane.org>
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-Y27EyoLml9s@public.gmane.org>
Date		: 2010-08-19 21:03 (39 days old)
Message-ID	: <alpine.SOC.1.00.1008192359310.19654-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
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-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Date		: 2010-08-18 6:18 (40 days old)
Message-ID	: <1282112318.21202.8.camel-sz7BYL/Y5Hu/P+R7jlPCFVaTQe2KTcn/@public.gmane.org>
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-agH9qYG3oEhmR6Xm/wNWPw@public.gmane.org>
Date		: 2010-09-22 15:42 (5 days old)
First-Bad-Commit: http://git.kernel.org/linus/e259befd9013e212648c3bd4f6f1fbf92d0dd51d
Handled-By	: Chris Wilson <chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>
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-ZHiucA87ovfk1uMJSBkQmQ@public.gmane.org>
Date		: 2010-09-15 14:35 (12 days old)
Message-ID	: <4C90D998.6050103-ZHiucA87ovfk1uMJSBkQmQ@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128456187928496&w=2
Handled-By	: Jesse Barnes <jbarnes-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.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 #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

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-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> Date		: 2010-09-23 0:54 (4 days old)
> Message-ID	: <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> 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

[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-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > Date		: 2010-09-23 0:54 (4 days old)
> > Message-ID	: <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > 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

[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-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > > Date		: 2010-09-23 0:54 (4 days old)
> > > Message-ID	: <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > > 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 #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 #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-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
>>>> Date		: 2010-09-23 0:54 (4 days old)
>>>> Message-ID	: <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
>>>> 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

[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-AlSwsSmVLrQ@public.gmane.org>
SUSE Labs, CR

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

[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

[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-KKrjLPT3xs0@public.gmane.org> 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-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > > Date		: 2010-09-23 0:54 (4 days old)
> > > Message-ID	: <4C9AA546.6050201-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org>
> > > 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-AlSwsSmVLrQ@public.gmane.org>
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

[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-AlSwsSmVLrQ@public.gmane.org>
> 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


				

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