* 2.6.36-rc5-git7: Reported regressions from 2.6.35
@ 2010-09-26 19:55 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 19:55 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Maciej Rutecki, Florian Mickler, Andrew Morton, Linus Torvalds,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
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!
^ permalink raw reply [flat|nested] 77+ messages in thread
* 2.6.36-rc5-git7: Reported regressions from 2.6.35
@ 2010-09-26 19:55 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 19:55 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Maciej Rutecki, Florian Mickler, Andrew Morton, Linus Torvalds,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
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!
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #16951] hackbench regression with 2.6.36-rc1
2010-09-26 19:55 ` Rafael J. Wysocki
@ 2010-09-26 19:55 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 19:55 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Zhang, Yanmin
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-09-26 19:55 ` Rafael J. Wysocki
(?)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
2010-10-02 16:52 ` Ted Ts'o
-1 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Christian Casteyde
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)
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-09-26 20:04 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
@ 2010-10-02 16:52 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-02 16:52 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Christian Casteyde
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
@ 2010-10-02 16:52 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-02 16:52 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Christian Casteyde
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-GANU6spQydw@public.gmane.org>
> 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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
@ 2010-10-03 11:21 ` Vegard Nossum
0 siblings, 0 replies; 77+ messages in thread
From: Vegard Nossum @ 2010-10-03 11:21 UTC (permalink / raw)
To: Ted Ts'o, Rafael J. Wysocki, Linux Kernel Mailing List,
Kernel Testers List, Maciej Rutecki, Florian Mickler,
Christian Casteyde
Cc: Frederic Weisbecker, Ingo Molnar, Mathieu Desnoyers
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
@ 2010-10-03 11:21 ` Vegard Nossum
0 siblings, 0 replies; 77+ messages in thread
From: Vegard Nossum @ 2010-10-03 11:21 UTC (permalink / raw)
To: Ted Ts'o, Rafael J. Wysocki, Linux Kernel Mailing List,
Kernel Testers List, Maciej
Cc: Frederic Weisbecker, Ingo Molnar, Mathieu Desnoyers
On 2 October 2010 18:52, Ted Ts'o <tytso-3s7WtUTddSA@public.gmane.org> 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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17121] Two blank rectangles more than 10 cm long when booting
2010-09-26 19:55 ` Rafael J. Wysocki
` (2 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-27 6:01 ` Eric Valette
-1 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Eric Valette
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)
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17121] Two blank rectangles more than 10 cm long when booting
2010-09-26 20:04 ` [Bug #17121] Two blank rectangles more than 10 cm long when booting Rafael J. Wysocki
@ 2010-09-27 6:01 ` Eric Valette
0 siblings, 0 replies; 77+ messages in thread
From: Eric Valette @ 2010-09-27 6:01 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17121] Two blank rectangles more than 10 cm long when booting
@ 2010-09-27 6:01 ` Eric Valette
0 siblings, 0 replies; 77+ messages in thread
From: Eric Valette @ 2010-09-27 6:01 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler
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-GANU6spQydw@public.gmane.org>
> Date : 2010-08-26 17:24 (32 days old)
>
>
Still present on 2.6.36-rc5-git7.
--eric
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17121] Two blank rectangles more than 10 cm long when booting
@ 2010-09-27 19:41 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-27 19:41 UTC (permalink / raw)
To: eric.valette
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #17121] Two blank rectangles more than 10 cm long when booting
@ 2010-09-27 19:41 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-27 19:41 UTC (permalink / raw)
To: eric.valette-GANU6spQydw
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler
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-GANU6spQydw@public.gmane.org>
> > Date : 2010-08-26 17:24 (32 days old)
> >
> >
>
> Still present on 2.6.36-rc5-git7.
Thanks for the update.
Rafael
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
2010-09-26 19:55 ` Rafael J. Wysocki
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Meelis Roos
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
@ 2010-09-26 20:04 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Meelis Roos
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 (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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17061] 2.6.36-rc1 on zaurus: bluetooth regression
2010-09-26 19:55 ` Rafael J. Wysocki
` (4 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Pavel Machek
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #18342] [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1
2010-09-26 19:55 ` Rafael J. Wysocki
` (5 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Woody Suwalski
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17722] 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed
2010-09-26 19:55 ` Rafael J. Wysocki
` (6 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Thomas Meyer
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #18742] PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop
2010-09-26 19:55 ` Rafael J. Wysocki
` (7 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, infernix,
Jesse Barnes
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #18962] screen failes in kde
2010-09-26 19:55 ` Rafael J. Wysocki
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler,
Chris Wilson, Hans de Bruin
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #18992] warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5
2010-09-26 19:55 ` Rafael J. Wysocki
` (9 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, rocko
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)
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
2010-09-26 19:55 ` Rafael J. Wysocki
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Mikael Pettersson
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
@ 2010-09-26 20:04 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Mikael Pettersson
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 (4 days old)
Message-ID : <19611.34846.813757.309183-tgku4HJDRZih8lFjZTKsyTAV6s6igYVG@public.gmane.org>
References : http://marc.info/?l=linux-kernel&m=128526136531048&w=2
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
2010-09-26 20:04 ` Rafael J. Wysocki
@ 2010-09-27 10:28 ` Mikael Pettersson
-1 siblings, 0 replies; 77+ messages in thread
From: Mikael Pettersson @ 2010-09-27 10:28 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, 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.
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
@ 2010-09-27 10:28 ` Mikael Pettersson
0 siblings, 0 replies; 77+ messages in thread
From: Mikael Pettersson @ 2010-09-27 10:28 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, 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-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=3Dlinux-kernel&m=3D128526136531048&w=3D2
Still present in 2.6.36-rc5.
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
@ 2010-09-27 19:43 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-27 19:43 UTC (permalink / raw)
To: Mikael Pettersson
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP
@ 2010-09-27 19:43 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-27 19:43 UTC (permalink / raw)
To: Mikael Pettersson
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler
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-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=3Dlinux-kernel&m=3D128526136531048&w=3D2
>
> Still present in 2.6.36-rc5.
Thanks for the update.
Rafael
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19052] 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
2010-09-26 19:55 ` Rafael J. Wysocki
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Miles Lane
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19052] 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
@ 2010-09-26 20:04 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Miles Lane
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-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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
2010-09-26 19:55 ` Rafael J. Wysocki
` (12 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
2010-10-02 16:54 ` Ted Ts'o
-1 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler,
Cesar Eduardo Barros
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
2010-09-26 20:04 ` [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs Rafael J. Wysocki
@ 2010-10-02 16:54 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-02 16:54 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-02 16:54 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-02 16:54 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-02 21:58 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-10-02 21:58 UTC (permalink / raw)
To: Ted Ts'o, Andrew Morton
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Tejun Heo, Jens Axboe
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?
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-02 21:58 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-10-02 21:58 UTC (permalink / raw)
To: Ted Ts'o, Andrew Morton
Cc: Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Tejun Heo, Jens Axboe
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?
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-03 2:27 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-03 2:27 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Andrew Morton, Linux Kernel Mailing List, Kernel Testers List,
Maciej Rutecki, Florian Mickler, Cesar Eduardo Barros, Tejun Heo,
Jens Axboe
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-03 2:27 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-03 2:27 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Andrew Morton, Linux Kernel Mailing List, Kernel Testers List,
Maciej Rutecki, Florian Mickler, Cesar Eduardo Barros, Tejun Heo,
Jens Axboe
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-03 15:16 ` Tejun Heo
0 siblings, 0 replies; 77+ messages in thread
From: Tejun Heo @ 2010-10-03 15:16 UTC (permalink / raw)
To: Ted Ts'o, Rafael J. Wysocki, Andrew Morton,
Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Jens Axboe, Jan Kara
(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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-03 15:16 ` Tejun Heo
0 siblings, 0 replies; 77+ messages in thread
From: Tejun Heo @ 2010-10-03 15:16 UTC (permalink / raw)
To: Ted Ts'o, Rafael J. Wysocki, Andrew Morton,
Linux Kernel Mailing List, Kernel
(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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 9:59 ` Jan Kara
0 siblings, 0 replies; 77+ messages in thread
From: Jan Kara @ 2010-10-04 9:59 UTC (permalink / raw)
To: Tejun Heo
Cc: Ted Ts'o, Rafael J. Wysocki, Andrew Morton,
Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Jens Axboe, Jan Kara,
Christoph Hellwig
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 9:59 ` Jan Kara
0 siblings, 0 replies; 77+ messages in thread
From: Jan Kara @ 2010-10-04 9:59 UTC (permalink / raw)
To: Tejun Heo
Cc: Ted Ts'o, Rafael J. Wysocki, Andrew Morton,
Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Jens Axboe, Jan Kara,
Christoph Hellwig
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 10:12 ` Christoph Hellwig
0 siblings, 0 replies; 77+ messages in thread
From: Christoph Hellwig @ 2010-10-04 10:12 UTC (permalink / raw)
To: Jan Kara
Cc: Tejun Heo, Ted Ts'o, Rafael J. Wysocki, Andrew Morton,
Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Jens Axboe,
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.
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 10:12 ` Christoph Hellwig
0 siblings, 0 replies; 77+ messages in thread
From: Christoph Hellwig @ 2010-10-04 10:12 UTC (permalink / raw)
To: Jan Kara
Cc: Tejun Heo, Ted Ts'o, Rafael J. Wysocki, Andrew Morton,
Linux Kernel Mailing List, Kernel Testers List, Maciej Rutecki,
Florian Mickler, Cesar Eduardo Barros, Jens Axboe,
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.
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 17:46 ` Jens Axboe
0 siblings, 0 replies; 77+ messages in thread
From: Jens Axboe @ 2010-10-04 17:46 UTC (permalink / raw)
To: Christoph Hellwig
Cc: Jan Kara, Tejun Heo, Ted Ts'o, Rafael J. Wysocki,
Andrew Morton, Linux Kernel Mailing List, Kernel Testers List,
Maciej Rutecki, Florian Mickler, Cesar Eduardo Barros
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 17:46 ` Jens Axboe
0 siblings, 0 replies; 77+ messages in thread
From: Jens Axboe @ 2010-10-04 17:46 UTC (permalink / raw)
To: Christoph Hellwig
Cc: Jan Kara, Tejun Heo, Ted Ts'o, Rafael J. Wysocki,
Andrew Morton, Linux Kernel Mailing List, Kernel Testers List,
Maciej Rutecki, Florian Mickler, Cesar Eduardo Barros
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 20:09 ` Andrew Morton
0 siblings, 0 replies; 77+ messages in thread
From: Andrew Morton @ 2010-10-04 20:09 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Ted Ts'o, Linux Kernel Mailing List, Kernel Testers List,
Maciej Rutecki, Florian Mickler, Cesar Eduardo Barros, Tejun Heo,
Jens Axboe, Christoph Hellwig, Jan Kara
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?
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-04 20:09 ` Andrew Morton
0 siblings, 0 replies; 77+ messages in thread
From: Andrew Morton @ 2010-10-04 20:09 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Ted Ts'o, Linux Kernel Mailing List, Kernel Testers List,
Maciej Rutecki, Florian Mickler, Cesar Eduardo Barros, Tejun Heo,
Jens Axboe, Christoph Hellwig, Jan Kara
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?
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-05 15:59 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-05 15:59 UTC (permalink / raw)
To: Andrew Morton
Cc: Rafael J. Wysocki, Linux Kernel Mailing List,
Kernel Testers List, Maciej Rutecki, Florian Mickler,
Cesar Eduardo Barros, Tejun Heo, Jens Axboe, Christoph Hellwig,
Jan Kara
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs
@ 2010-10-05 15:59 ` Ted Ts'o
0 siblings, 0 replies; 77+ messages in thread
From: Ted Ts'o @ 2010-10-05 15:59 UTC (permalink / raw)
To: Andrew Morton
Cc: Rafael J. Wysocki, Linux Kernel Mailing List,
Kernel Testers List, Maciej Rutecki, Florian Mickler,
Cesar Eduardo Barros, Tejun Heo, Jens Axboe, Christoph Hellwig,
Jan Kara
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19002] Radeon rv730 AGP/KMS/DRM kernel lockup
2010-09-26 19:55 ` Rafael J. Wysocki
@ 2010-09-26 20:04 ` Rafael J. Wysocki
-1 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Duncan
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)
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19002] Radeon rv730 AGP/KMS/DRM kernel lockup
@ 2010-09-26 20:04 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Duncan
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-j9pdmedNgrk@public.gmane.org>
Date : 2010-09-23 16:48 (4 days old)
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #19082] fs/fs-writeback.c to dump
2010-09-26 19:55 ` Rafael J. Wysocki
` (14 preceding siblings ...)
(?)
@ 2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 23:40 ` Pavel Vasilyev
-1 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-26 20:04 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Pavel Vasilyev
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
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug #19082] fs/fs-writeback.c to dump
2010-09-26 20:04 ` [Bug #19082] fs/fs-writeback.c to dump Rafael J. Wysocki
@ 2010-09-26 23:40 ` Pavel Vasilyev
0 siblings, 0 replies; 77+ messages in thread
From: Pavel Vasilyev @ 2010-09-26 23:40 UTC (permalink / raw)
To: Rafael J. Wysocki, linux-kernel
[-- 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 --]
^ permalink raw reply [flat|nested] 77+ messages in thread
* 2.6.36-rc6-git2: Reported regressions from 2.6.35
@ 2010-10-03 21:15 Rafael J. Wysocki
2010-10-03 21:19 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
0 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-10-03 21:15 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Maciej Rutecki, Florian Mickler, Andrew Morton, Linus Torvalds,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
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!
^ permalink raw reply [flat|nested] 77+ messages in thread
* 2.6.36-rc4-git5: Reported regressions from 2.6.35
@ 2010-09-20 18:47 Rafael J. Wysocki
2010-09-20 19:08 ` Rafael J. Wysocki
0 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-20 18:47 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Maciej Rutecki, Florian Mickler, Andrew Morton, Linus Torvalds,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
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-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=18872
Subject : Radeon KMS r100 and STR problems
Submitter : Richard Mittendorfer <delist@gmx.net>
Date : 2010-09-17 18:26 (4 days old)
Message-ID : <20100917202647.aa4b6300.delist@gmx.net>
References : http://marc.info/?l=linux-kernel&m=128474802809779&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18862
Subject : [BUG]Kernel 2.6.36rc4 crash when rmmod pm8001
Submitter : Jack Wang <jack_wang@usish.com>
Date : 2010-09-17 10:11 (4 days old)
Message-ID : <3219F4D1734640238A632382C50F633E@usish.com.cn>
References : http://marc.info/?l=linux-kernel&m=128471846828998&w=2
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 (6 days old)
Message-ID : <4C90D998.6050103@infernix.net>
References : http://marc.info/?l=linux-kernel&m=128456187928496&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18692
Subject : 2.6.36-rc4/iwl: warning triggered in net/mac80211/scan.c:266
Submitter : Michael S. Tsirkin <mst@redhat.com>
Date : 2010-09-14 14:28 (7 days old)
Message-ID : <20100914142814.GA8744@redhat.com>
References : http://marc.info/?l=linux-kernel&m=128447487918792&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18432
Subject : radeon kms freezes on boot with video= option
Submitter : Jose Marino <braket@hotmail.com>
Date : 2010-09-13 22:28 (8 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18402
Subject : 2.6.36-rc4 KPs whenever booting on a Pentium 4 HT system
Submitter : Michael Marley <michael@michaelmarley.com>
Date : 2010-09-13 15:07 (8 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 (13 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=18332
Subject : [regression] *ERROR* timed out waiting for FORCE_DETECT in 36rc3 on i915
Submitter : Andi Kleen <andi@firstfloor.org>
Date : 2010-09-08 13:53 (13 days old)
Message-ID : <87mxrswddf.fsf@basil.nowhere.org>
References : http://marc.info/?l=linux-kernel&m=128395400624946&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17752
Subject : 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)
Submitter : Stefan Richter <stefanr@s5r6.in-berlin.de>
Date : 2010-09-01 6:37 (20 days old)
Message-ID : <tkrat.ed8eda6bc8ffe64e@s5r6.in-berlin.de>
References : http://marc.info/?l=linux-kernel&m=128332308528119&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 (21 days old)
Message-ID : <201008312214.52473.thomas@m3y3r.de>
References : http://marc.info/?l=linux-kernel&m=128328580504227&w=2
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 (23 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17341
Subject : kdump regression compared to v2.6.35
Submitter : CAI Qian <caiqian@redhat.com>
Date : 2010-08-27 12:35 (25 days old)
Message-ID : <2136707099.1405541282912500148.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
References : http://marc.info/?l=linux-kernel&m=128291252612135&w=2
Handled-By : Tejun Heo <tj@kernel.org>
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 (31 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 (33 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 (34 days old)
Message-ID : <1282112318.21202.8.camel@ymzhang.sh.intel.com>
References : http://marc.info/?l=linux-kernel&m=128211235904910&w=2
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions 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!
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-09-20 18:47 2.6.36-rc4-git5: Reported regressions from 2.6.35 Rafael J. Wysocki
@ 2010-09-20 19:08 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-20 19:08 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Christian Casteyde
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 (23 days old)
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
@ 2010-09-20 19:08 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-20 19:08 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Florian Mickler, Christian Casteyde
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-GANU6spQydw@public.gmane.org>
Date : 2010-08-29 19:59 (23 days old)
^ permalink raw reply [flat|nested] 77+ messages in thread
* 2.6.36-rc3-git5: Reported regressions from 2.6.35
@ 2010-09-12 18:11 Rafael J. Wysocki
2010-09-12 18:14 ` Rafael J. Wysocki
0 siblings, 1 reply; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-12 18:11 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Maciej Rutecki, Florian Mickler, Andrew Morton, Linus Torvalds,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
[NOTE:
Florian Mickler has joined the regression tracking team. He is going to
browse the list periodically to close fixed regressions, add patches etc.
So, when the listed regressions you care about are fixed, please report
that to Florian. If there's a working patch for a regression you care
about, please report that to him too.]
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-12 28 14 13
2010-08-30 21 16 15
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17952
Subject : bdi-default hung waiting for kthread_stop to finish
Submitter : Jeff Layton <jlayton@redhat.com>
Date : 2010-09-02 18:55 (11 days old)
Message-ID : <20100902145509.28e4f998@tlielax.poochiereds.net>
References : http://marc.info/?l=linux-kernel&m=128345371904504&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17752
Subject : 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)
Submitter : Stefan Richter <stefanr@s5r6.in-berlin.de>
Date : 2010-09-01 6:37 (12 days old)
Message-ID : <tkrat.ed8eda6bc8ffe64e@s5r6.in-berlin.de>
References : http://marc.info/?l=linux-kernel&m=128332308528119&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 (13 days old)
Message-ID : <201008312214.52473.thomas@m3y3r.de>
References : http://marc.info/?l=linux-kernel&m=128328580504227&w=2
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 (15 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17341
Subject : kdump regression compared to v2.6.35
Submitter : CAI Qian <caiqian@redhat.com>
Date : 2010-08-27 12:35 (17 days old)
Message-ID : <2136707099.1405541282912500148.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
References : http://marc.info/?l=linux-kernel&m=128291252612135&w=2
Handled-By : Tejun Heo <tj@kernel.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17331
Subject : BUG: scheduling while atomic
Submitter : Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date : 2010-08-27 7:59 (17 days old)
Message-ID : <20100827075911.GA5966@swordfish.minsk.epam.com>
References : http://marc.info/?l=linux-kernel&m=128289602925505&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17321
Subject : i386 WARNING: at kernel/softirq.c:143 _local_bh_enable_ip+0x2f/0x7e
Submitter : Arno Schuring <aelschuring@hotmail.com>
Date : 2010-08-27 20:04 (17 days old)
Message-ID : <4C781A3A.4010707@hotmail.com>
References : http://marc.info/?l=linux-kernel&m=128294076822387&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17311
Subject : 2.6.36-rc2-git4 - INFO: possible circular locking dependency detected
Submitter : Miles Lane <miles.lane@gmail.com>
Date : 2010-08-27 1:56 (17 days old)
First-Bad-Commit: http://git.kernel.org/linus/5a652052fedbd7869572c757dd2ffc2ed420c69d
Message-ID : <AANLkTinHbEW36D5R9NSrGgfbOC0Hri3Tg-fA0iR92Udi@mail.gmail.com>
References : http://marc.info/?l=linux-kernel&m=128287422106267&w=2
Handled-By : Johannes Berg <johannes@sipsolutions.net>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17131
Subject : WARN with 3c905 boomerang NIC
Submitter : Doug Nazar <nazard.lkml@gmail.com>
Date : 2010-08-22 6:35 (22 days old)
Message-ID : <4C70C516.5020404@gmail.com>
References : http://marc.info/?l=linux-kernel&m=128245894300623&w=2
Handled-By : David Miller <davem@davemloft.net>
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 (23 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 (25 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=16961
Subject : kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978
Submitter : Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date : 2010-08-19 9:54 (25 days old)
Message-ID : <<20100819095429.GA5201@swordfish.minsk.epam.com>>
References : http://marc.info/?l=linux-kernel&m=128221169606214&w=2
Handled-By : Avi Kivity <avi@redhat.com>
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 (26 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=17742
Subject : 2.6.36-rc2-git5: Oops in snd_pcm_substream_proc_status_read()
Submitter : Chuck Ebbert <cebbert@redhat.com>
Date : 2010-09-01 8:19 (12 days old)
Message-ID : <20100901041924.23a8a865@katamari>
References : http://marc.info/?l=linux-kernel&m=128332930703451&w=2
https://bugzilla.redhat.com/show_bug.cgi?id=628404
https://bugzilla.redhat.com/show_bug.cgi?id=628404#c5
Handled-By : Takashi Iwai <tiwai@suse.de>
Patch : http://mailman.alsa-project.org/pipermail/alsa-devel/2010-September/031275.html
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions 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!
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-09-12 18:11 2.6.36-rc3-git5: Reported regressions from 2.6.35 Rafael J. Wysocki
@ 2010-09-12 18:14 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-12 18:14 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Christian Casteyde
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 (15 days old)
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
@ 2010-09-12 18:14 ` Rafael J. Wysocki
0 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-09-12 18:14 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Kernel Testers List, Maciej Rutecki, Christian Casteyde
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-GANU6spQydw@public.gmane.org>
Date : 2010-08-29 19:59 (15 days old)
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] New: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
@ 2010-08-29 20:00 bugzilla-daemon
2010-09-07 22:05 ` [Bug 17361] " bugzilla-daemon
` (16 more replies)
0 siblings, 17 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-08-29 20:00 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
Summary: Watchdog detected hard LOCKUP in
jbd2_journal_get_write_access
Product: File System
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext3
AssignedTo: fs_ext3@kernel-bugs.osdl.org
ReportedBy: casteyde.christian@free.fr
Regression: Yes
Created an attachment (id=28361)
--> (https://bugzilla.kernel.org/attachment.cgi?id=28361)
full dmesg output
Kernel configuration: 2.6.36-rc3
Athlon 64 X2 3GHz in 64bits mode
Slackware64 13.1
maybe an ext4 problem
At boot, with a kernel compiled with support for locks, kmemcheck and so, I got
this from time to time (amoung several other problems reported from kmemcheck
and sometimes a total freeze at boot):
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): mounted filesystem with ordered data mode
ADDRCONF(NETDEV_UP): eth0: link is not ready
uli526x: eth0 NIC Link is Up 100 Mbps Full duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
------------[ cut here ]------------
WARNING: at kernel/watchdog.c:233 watchdog_overflow_callback+0xe3/0x110()
Hardware name: K8 Combo-Z
Watchdog detected hard LOCKUP on cpu 0
Modules linked in: snd_intel8x0 snd_cmipci snd_opl3_lib snd_hwdep
snd_mpu401_uart snd_ac97_codec snd_ra
wmidi ac97_bus
Pid: 1923, comm: update-mime-dat Not tainted 2.6.36-rc3 #6
Call Trace:
<NMI> [<ffffffff81042cda>] warn_slowpath_common+0x7a/0xb0
[<ffffffff81042db1>] warn_slowpath_fmt+0x41/0x50
[<ffffffff81086d37>] ? watchdog_overflow_callback+0x7/0x110
[<ffffffff81086e13>] watchdog_overflow_callback+0xe3/0x110
[<ffffffff81096281>] ? __perf_event_overflow+0x141/0x210
[<ffffffff8109133a>] ? perf_event_update_userpage+0x10a/0x1b0
[<ffffffff81091230>] ? perf_event_update_userpage+0x0/0x1b0
[<ffffffff8101247d>] ? x86_perf_event_set_period+0xdd/0x160
[<ffffffff810964f4>] ? perf_event_overflow+0x14/0x20
[<ffffffff8101414f>] ? x86_pmu_handle_irq+0x10f/0x140
[<ffffffff81010d8b>] ? perf_event_nmi_handler+0x4b/0x60
[<ffffffff810660d0>] ? notifier_call_chain+0x50/0xa0
[<ffffffff810666a5>] ? __atomic_notifier_call_chain+0x95/0xd0
[<ffffffff81066610>] ? __atomic_notifier_call_chain+0x0/0xd0
[<ffffffff8108b255>] ? rcu_nmi_exit+0x15/0x60
[<ffffffff8100424b>] ? do_nmi+0x9b/0x2b0
[<ffffffff815981ca>] ? nmi+0x1a/0x2c
[<ffffffff8118fc46>] ? jbd2_journal_get_write_access+0x36/0x50
[<ffffffff81597de0>] ? debug+0x0/0x40
<<EOE>> <#DB> [<ffffffff81086d42>] ? watchdog_overflow_callback+0x12/0x110
<<EOE>>
---[ end trace 1408e87e8e109015 ]---
BUG: sleeping function called from invalid context at fs/ext4/inode.c:5833
in_atomic(): 1, irqs_disabled(): 0, pid: 1923, name: update-mime-dat
2 locks held by update-mime-dat/1923:
#0: (&sb->s_type->i_mutex_key#3){+.+.+.}, at: [<ffffffff810db511>]
do_last+0x111/0x690
#1: (jbd2_handle){+.+...}, at: [<ffffffff811904f0>]
start_this_handle+0x470/0x510
Pid: 1923, comm: update-mime-dat Tainted: G W 2.6.36-rc3 #6
Call Trace:
[<ffffffff810721f3>] ? __debug_show_held_locks+0x13/0x30
[<ffffffff81036b85>] __might_sleep+0x105/0x130
[<ffffffff8115c137>] ext4_mark_inode_dirty+0x47/0x1d0
[<ffffffff8116643b>] ext4_add_nondir+0x6b/0x80
[<ffffffff81166bf6>] ext4_create+0xd6/0x130
[<ffffffff810da459>] vfs_create+0x89/0xc0
[<ffffffff810db9fa>] ? do_last+0x5fa/0x690
[<ffffffff810db935>] do_last+0x535/0x690
[<ffffffff810dd97d>] do_filp_open+0x21d/0x660
[<ffffffff81596c98>] ? trace_hardirqs_off_thunk+0x3a/0x3c
[<ffffffff810393c5>] ? sub_preempt_count+0x95/0xd0
[<ffffffff815977d0>] ? _raw_spin_unlock+0x30/0x60
[<ffffffff810e9132>] ? alloc_fd+0x122/0x1d0
[<ffffffff810cd7e0>] do_sys_open+0x60/0x120
[<ffffffff81596c59>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810cd8cb>] sys_open+0x1b/0x20
[<ffffffff810023ab>] system_call_fastpath+0x16/0x1b
note: update-mime-dat[1923] exited with preempt_count 1
BUG: scheduling while atomic: update-mime-dat/1923/0x10000002
no locks held by update-mime-dat/1923.
Modules linked in: snd_intel8x0 snd_cmipci snd_opl3_lib snd_hwdep
snd_mpu401_uart snd_ac97_codec snd_rawmidi ac97_bus
Pid: 1923, comm: update-mime-dat Tainted: G W 2.6.36-rc3 #6
Call Trace:
[<ffffffff810721f3>] ? __debug_show_held_locks+0x13/0x30
[<ffffffff81039257>] __schedule_bug+0x77/0x80
[<ffffffff815943f9>] schedule+0x6e9/0xa30
[<ffffffff8103d153>] __cond_resched+0x13/0x30
[<ffffffff8159482b>] _cond_resched+0x2b/0x40
[<ffffffff810b1a59>] unmap_vmas+0x7c9/0x940
[<ffffffff810b6c2d>] exit_mmap+0xdd/0x1a0
[<ffffffff81040677>] mmput+0x57/0xe0
[<ffffffff81045250>] exit_mm+0x100/0x130
[<ffffffff810477ad>] do_exit+0x64d/0x720
[<ffffffff810478cf>] do_group_exit+0x4f/0xc0
[<ffffffff8105448a>] get_signal_to_deliver+0x31a/0x510
[<ffffffff81040090>] ? kick_process+0x50/0xa0
[<ffffffff8159778d>] ? _raw_spin_unlock_irqrestore+0x5d/0x70
[<ffffffff810017c0>] do_signal+0x70/0x790
[<ffffffff8159776d>] ? _raw_spin_unlock_irqrestore+0x3d/0x70
[<ffffffff8100dd71>] ? syscall_trace_leave+0xd1/0xe0
[<ffffffff81001f2f>] do_notify_resume+0x4f/0x60
[<ffffffff81596c59>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff8100264b>] int_signal+0x12/0x17
BUG: scheduling while atomic: update-mime-dat/1923/0x10000002
no locks held by update-mime-dat/1923.
Modules linked in: snd_intel8x0 snd_cmipci snd_opl3_lib snd_hwdep
snd_mpu401_uart snd_ac97_codec snd_rawmidi ac97_bus
Pid: 1923, comm: update-mime-dat Tainted: G W 2.6.36-rc3 #6
Call Trace:
...
etc
full dmesg appended as attachement.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
@ 2010-09-07 22:05 ` bugzilla-daemon
2010-09-07 22:27 ` bugzilla-daemon
` (15 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-07 22:05 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
Andrew Morton <akpm@linux-foundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |akpm@linux-foundation.org
Component|ext3 |ext4
AssignedTo|fs_ext3@kernel-bugs.osdl.or |fs_ext4@kernel-bugs.osdl.or
|g |g
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
2010-09-07 22:05 ` [Bug 17361] " bugzilla-daemon
@ 2010-09-07 22:27 ` bugzilla-daemon
2010-09-14 5:48 ` bugzilla-daemon
` (14 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-07 22:27 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
Rafael J. Wysocki <rjw@sisk.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |maciej.rutecki@gmail.com,
| |rjw@sisk.pl
Kernel Version| |2.6.36-rc3
Blocks| |16444
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
2010-09-07 22:05 ` [Bug 17361] " bugzilla-daemon
2010-09-07 22:27 ` bugzilla-daemon
@ 2010-09-14 5:48 ` bugzilla-daemon
2010-09-14 5:51 ` bugzilla-daemon
` (13 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-14 5:48 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #1 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-14 05:48:04 ---
Update :
still present in 2.6.36-rc4.
However, the call stack is a little different now. As the computer crashes very
soon, I've taken a photo, see attachment.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (2 preceding siblings ...)
2010-09-14 5:48 ` bugzilla-daemon
@ 2010-09-14 5:51 ` bugzilla-daemon
2010-09-14 18:08 ` bugzilla-daemon
` (12 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-14 5:51 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #2 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-14 05:50:55 ---
Created an attachment (id=29872)
--> (https://bugzilla.kernel.org/attachment.cgi?id=29872)
console output image
screenshot of warning (can't get it as the computer crashes after that).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (3 preceding siblings ...)
2010-09-14 5:51 ` bugzilla-daemon
@ 2010-09-14 18:08 ` bugzilla-daemon
2010-09-21 17:19 ` bugzilla-daemon
` (11 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-14 18:08 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #3 from Rafael J. Wysocki <rjw@sisk.pl> 2010-09-14 18:08:31 ---
On Tuesday, September 14, 2010, Christian Casteyde wrote:
> Yes, still present, as well as my other bug that says that the system freezes
> short after the boot.
>
> Le dimanche 12 septembre 2010 20:14:29, vous avez écrit :
> > 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 (15 days old)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (4 preceding siblings ...)
2010-09-14 18:08 ` bugzilla-daemon
@ 2010-09-21 17:19 ` bugzilla-daemon
2010-09-22 17:48 ` bugzilla-daemon
` (10 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-21 17:19 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #4 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-21 17:19:32 ---
Update : Still present in 2.6.36-rc5
With the same log as shown in comment #2
Some more info are given after that ("recursive fault fixed, but rebbot is
necessary").
If I wait a little more, I get another pile of messages.
More precisely, the problem occurs indeed after dhcp gets an IP address, and
before (or when) sshd is started. Between the two, I guess iptables rules are
defined in my network scripts.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (5 preceding siblings ...)
2010-09-21 17:19 ` bugzilla-daemon
@ 2010-09-22 17:48 ` bugzilla-daemon
2010-09-22 17:51 ` bugzilla-daemon
` (9 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 17:48 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #5 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 17:47:58 ---
Well, I managed to boot in single mode, and tried to execute commands one by
one to see what triggers the problems.
Indeed, it's really random, sometime it's while ldconfig is called by the init
scripts, sometime it's when starting udev...
The callstacks are quite different also, sometime it's kmemcheck, sometime
preempt count, sometime NULL dereference...
So I'm posting the dmesg output I saved each time I got an error. Now at least
they are complete, so the root cause may be easier to find.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (6 preceding siblings ...)
2010-09-22 17:48 ` bugzilla-daemon
@ 2010-09-22 17:51 ` bugzilla-daemon
2010-09-22 17:53 ` bugzilla-daemon
` (8 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 17:51 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #6 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 17:51:41 ---
Created an attachment (id=30982)
--> (https://bugzilla.kernel.org/attachment.cgi?id=30982)
warning got while booting
kmemcheck fatal error while in sys_readlink
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (7 preceding siblings ...)
2010-09-22 17:51 ` bugzilla-daemon
@ 2010-09-22 17:53 ` bugzilla-daemon
2010-09-22 17:56 ` bugzilla-daemon
` (7 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 17:53 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #7 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 17:53:31 ---
Created an attachment (id=30992)
--> (https://bugzilla.kernel.org/attachment.cgi?id=30992)
warning got while starting udev
now using smp_processor_id() in preemptible while in watchdog_overflow_callback
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (8 preceding siblings ...)
2010-09-22 17:53 ` bugzilla-daemon
@ 2010-09-22 17:56 ` bugzilla-daemon
2010-09-22 17:58 ` bugzilla-daemon
` (6 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 17:56 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #8 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 17:55:59 ---
Created an attachment (id=31002)
--> (https://bugzilla.kernel.org/attachment.cgi?id=31002)
quite the same, plus another warning after
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (9 preceding siblings ...)
2010-09-22 17:56 ` bugzilla-daemon
@ 2010-09-22 17:58 ` bugzilla-daemon
2010-09-22 18:01 ` bugzilla-daemon
` (5 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 17:58 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #9 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 17:58:50 ---
Created an attachment (id=31012)
--> (https://bugzilla.kernel.org/attachment.cgi?id=31012)
finally, the NULL dereference
I'm not sure the second and next warnings are not due to the first one, and a
bug in kmemcheck itself.
I'm totally unable to tell what cause it, and I gave up bisecting because it
crashes here and there, and I cannot say what crash is due to which bug, if
ever there is only one bug.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (10 preceding siblings ...)
2010-09-22 17:58 ` bugzilla-daemon
@ 2010-09-22 18:01 ` bugzilla-daemon
2010-09-22 18:11 ` bugzilla-daemon
` (4 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 18:01 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #10 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 18:01:49 ---
Created an attachment (id=31032)
--> (https://bugzilla.kernel.org/attachment.cgi?id=31032)
.config file
I append the .config file, just to tell what are the kernel debug options I
use.
I'm running in 64bit and build from vanilla source, with gcc 4.4.4.
I don't think this is hardware related, since I get the same on my laptop. More
some racy problems in udev/ldconfig/fc-cache
I'm still thinking it's a vfs problem or kmemcheck itself bug.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (11 preceding siblings ...)
2010-09-22 18:01 ` bugzilla-daemon
@ 2010-09-22 18:11 ` bugzilla-daemon
2010-09-22 18:13 ` bugzilla-daemon
` (3 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 18:11 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #11 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 18:11:39 ---
*** Bug 17371 has been marked as a duplicate of this bug. ***
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (12 preceding siblings ...)
2010-09-22 18:11 ` bugzilla-daemon
@ 2010-09-22 18:13 ` bugzilla-daemon
2010-09-27 19:26 ` bugzilla-daemon
` (2 subsequent siblings)
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-22 18:13 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #12 from Christian Casteyde <casteyde.christian@free.fr> 2010-09-22 18:13:08 ---
*** Bug 16616 has been marked as a duplicate of this bug. ***
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (13 preceding siblings ...)
2010-09-22 18:13 ` bugzilla-daemon
@ 2010-09-27 19:26 ` bugzilla-daemon
2010-10-02 16:42 ` bugzilla-daemon
2010-10-04 18:48 ` bugzilla-daemon
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-09-27 19:26 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #13 from Rafael J. Wysocki <rjw@sisk.pl> 2010-09-27 19:26:48 ---
On Monday, September 27, 2010, Christian Casteyde wrote:
> Still present in rc5-git7.
>
>
> Le dimanche 26 septembre 2010 22:04:13, vous avez écrit :
> > 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)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (14 preceding siblings ...)
2010-09-27 19:26 ` bugzilla-daemon
@ 2010-10-02 16:42 ` bugzilla-daemon
2010-10-11 20:43 ` Andreas Dilger
2010-10-04 18:48 ` bugzilla-daemon
16 siblings, 1 reply; 77+ messages in thread
From: bugzilla-daemon @ 2010-10-02 16:42 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #14 from Theodore Tso <tytso@mit.edu> 2010-10-02 16:42:45 ---
People may not be paying attention to this due to the subject line.
Except for the initial bug report, none of the other stack traces have anything
to do with ext4/jbd2. And in the initial ext4 trace, we see the complaint
that we're calling might_sleep() in ext4_mark_inode_dirty(), in a code path
where we are manifestly not taking any spinlocks. And in fact we don't see
any spinlocks being taken at the point where the complaint is mode in
ext4_mark_inode_dirty(). Yet preempt_count > 1.
It looks to me like some unrelated piece of code is bumping preempt_count, and
not decrementing it. Maybe in some code which is called from an interrupt
handler, in some device driver? That might explain why you're getting
failures all over the kernel.
It may be worth closing this report, and opening several new ones, one for each
failure, and make it clear this is not an ext4-related problem, since the
subject line and component assigned for this bug is highly misleading.
Including your kernel config would also be useful when you do that.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
* Re: [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-10-02 16:42 ` bugzilla-daemon
@ 2010-10-11 20:43 ` Andreas Dilger
0 siblings, 0 replies; 77+ messages in thread
From: Andreas Dilger @ 2010-10-11 20:43 UTC (permalink / raw)
To: Christian Casteyde; +Cc: linux-ext4 development
On 2010-10-02, at 09:42, Theodore Tso <tytso@mit.edu> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=17361
>
> Except for the initial bug report, none of the other stack traces have anything to do with ext4/jbd2. And in the initial ext4 trace, we see the complaint that we're calling might_sleep() in ext4_mark_inode_dirty(), in a code path where we are manifestly not taking any spinlocks. And in fact we don't see any spinlocks being taken at the point where the complaint is mode in ext4_mark_inode_dirty(). Yet preempt_count > 1.
In my experience, this is typically caused by stack overflow smashing the task struct and randomly setting preempt_count to a non-zero value.
Cheers, Andreas
^ permalink raw reply [flat|nested] 77+ messages in thread
* [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
` (15 preceding siblings ...)
2010-10-02 16:42 ` bugzilla-daemon
@ 2010-10-04 18:48 ` bugzilla-daemon
16 siblings, 0 replies; 77+ messages in thread
From: bugzilla-daemon @ 2010-10-04 18:48 UTC (permalink / raw)
To: linux-ext4
https://bugzilla.kernel.org/show_bug.cgi?id=17361
--- Comment #15 from Christian Casteyde <casteyde.christian@free.fr> 2010-10-04 18:48:29 ---
I've explored some of the ideas you mentionned.
First, I disabled kmemcheck, and indeed I've got no warning at all. So this is
really a kmemcheck + something else (buggy driver or perf counters as
mentionned by Vegard in his previous mail).
I could check the reverse: kmemcheck but without perf counters, however I
cannot unselect the perf option on my config (it is forced by something else
I've not found). kmemcheck used to work (I don't know if perf counters were
available in previous kernels however).
Second, I have most of my drivers built in, however I use sound cards as
modules in order to control the load order.
I've booted after erasing the /lib/module driver, but with kmemcheck enabled,
and it was far better. I got only one kmemecheck error:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
ERROR: kmemcheck: Fatal error
Pid: 1914, comm: gtk-update-icon Not tainted 2.6.36-rc6 #13 K8 Combo-Z/K8
Combo-Z
RIP: 0010:[<ffffffff81010b90>] [<ffffffff81010b90>]
x86_perf_event_update+0x0/0x80
RSP: 0018:ffff880002607d50 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000ffffffff
RDX: ffff88000260b5c0 RSI: 0000000000000400 RDI: ffff88003f808800
RBP: ffff880002607df8 R08: 0000000000000000 R09: 0000000000000004
R10: 0000000000000001 R11: 0000000000000038 R12: ffff88000260b7c8
R13: 0000000000000000 R14: ffff88000260b7c0 R15: ffff88003f808800
FS: 00007fdb70d5e700(0000) GS:ffff880002600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88003f836420 CR3: 000000003da52000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff4ff0 DR7: 0000000000000400
[<ffffffff8102bc34>] kmemcheck_error_save_bug+0xb4/0xe0
[<ffffffff8102c658>] kmemcheck_access+0xe8/0x4a0
[<ffffffff8102ca82>] kmemcheck_fault+0x72/0x80
[<ffffffff81026f89>] do_page_fault+0x359/0x440
[<ffffffff8159711f>] page_fault+0x1f/0x30
[<ffffffff81011528>] perf_event_nmi_handler+0x78/0x140
[<ffffffff810665d0>] notifier_call_chain+0x50/0xa0
[<ffffffff81066b81>] __atomic_notifier_call_chain+0x71/0xd0
[<ffffffff81066bf1>] atomic_notifier_call_chain+0x11/0x20
[<ffffffff81066c2e>] notify_die+0x2e/0x30
[<ffffffff81004343>] do_nmi+0x193/0x2b0
[<ffffffff8159740a>] nmi+0x1a/0x2c
[<ffffffff8102c5c7>] kmemcheck_access+0x57/0x4a0
[<ffffffff8102ca82>] kmemcheck_fault+0x72/0x80
[<ffffffff81026f89>] do_page_fault+0x359/0x440
[<ffffffff8159711f>] page_fault+0x1f/0x30
[<ffffffff810dab55>] do_lookup+0x55/0x170
[<ffffffff810dcb10>] link_path_walk+0x130/0xbd0
[<ffffffff810dd720>] path_walk+0x60/0xe0
[<ffffffff810dd7f3>] do_path_lookup+0x53/0x60
[<ffffffff810de433>] user_path_at+0x53/0xa0
[<ffffffff810d4c17>] vfs_fstatat+0x37/0x70
[<ffffffff810d4c86>] vfs_stat+0x16/0x20
[<ffffffff810d4e5f>] sys_newstat+0x1f/0x50
[<ffffffff810023ab>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
The good news is all other errors are gone. Here is the lsmod output without
kmemcheck, just to tell the modules that could cause more grief:
Module Size Used by
snd_intel8x0 29098 1
snd_cmipci 31770 4
snd_opl3_lib 9332 1 snd_cmipci
snd_hwdep 6314 1 snd_opl3_lib
snd_mpu401_uart 6360 1 snd_cmipci
snd_rawmidi 20342 1 snd_mpu401_uart
snd_ac97_codec 117688 1 snd_intel8x0
ac97_bus 1290 1 snd_ac97_codec
The .config file is already attached to this bug report (please note I've also
some other unused drivers configured, for hardware I do not use for now).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 77+ messages in thread
end of thread, other threads:[~2010-10-11 20:47 UTC | newest]
Thread overview: 77+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-26 19:55 2.6.36-rc5-git7: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-26 19:55 ` Rafael J. Wysocki
2010-09-26 19:55 ` [Bug #16951] hackbench regression with 2.6.36-rc1 Rafael J. Wysocki
2010-09-26 19:55 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-10-02 16:52 ` Ted Ts'o
2010-10-02 16:52 ` Ted Ts'o
2010-10-03 11:21 ` Vegard Nossum
2010-10-03 11:21 ` Vegard Nossum
2010-09-26 20:04 ` [Bug #17121] Two blank rectangles more than 10 cm long when booting Rafael J. Wysocki
2010-09-27 6:01 ` Eric Valette
2010-09-27 6:01 ` Eric Valette
2010-09-27 19:41 ` Rafael J. Wysocki
2010-09-27 19:41 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17061] 2.6.36-rc1 on zaurus: bluetooth regression Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18342] [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17722] 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18742] PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18962] screen failes in kde Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18992] warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-27 10:28 ` Mikael Pettersson
2010-09-27 10:28 ` Mikael Pettersson
2010-09-27 19:43 ` Rafael J. Wysocki
2010-09-27 19:43 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19052] 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs Rafael J. Wysocki
2010-10-02 16:54 ` Ted Ts'o
2010-10-02 16:54 ` Ted Ts'o
2010-10-02 21:58 ` Rafael J. Wysocki
2010-10-02 21:58 ` Rafael J. Wysocki
2010-10-03 2:27 ` Ted Ts'o
2010-10-03 2:27 ` Ted Ts'o
2010-10-03 15:16 ` Tejun Heo
2010-10-03 15:16 ` Tejun Heo
2010-10-04 9:59 ` Jan Kara
2010-10-04 9:59 ` Jan Kara
2010-10-04 10:12 ` Christoph Hellwig
2010-10-04 10:12 ` Christoph Hellwig
2010-10-04 17:46 ` Jens Axboe
2010-10-04 17:46 ` Jens Axboe
2010-10-04 20:09 ` Andrew Morton
2010-10-04 20:09 ` Andrew Morton
2010-10-05 15:59 ` Ted Ts'o
2010-10-05 15:59 ` Ted Ts'o
2010-09-26 20:04 ` [Bug #19002] Radeon rv730 AGP/KMS/DRM kernel lockup Rafael J. Wysocki
2010-09-26 20:04 ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19082] fs/fs-writeback.c to dump Rafael J. Wysocki
2010-09-26 23:40 ` Pavel Vasilyev
-- strict thread matches above, loose matches on Subject: below --
2010-10-03 21:15 2.6.36-rc6-git2: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-10-03 21:19 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-09-20 18:47 2.6.36-rc4-git5: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-20 19:08 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-09-20 19:08 ` Rafael J. Wysocki
2010-09-12 18:11 2.6.36-rc3-git5: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-12 18:14 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-09-12 18:14 ` Rafael J. Wysocki
2010-08-29 20:00 [Bug 17361] New: " bugzilla-daemon
2010-09-07 22:05 ` [Bug 17361] " bugzilla-daemon
2010-09-07 22:27 ` bugzilla-daemon
2010-09-14 5:48 ` bugzilla-daemon
2010-09-14 5:51 ` bugzilla-daemon
2010-09-14 18:08 ` bugzilla-daemon
2010-09-21 17:19 ` bugzilla-daemon
2010-09-22 17:48 ` bugzilla-daemon
2010-09-22 17:51 ` bugzilla-daemon
2010-09-22 17:53 ` bugzilla-daemon
2010-09-22 17:56 ` bugzilla-daemon
2010-09-22 17:58 ` bugzilla-daemon
2010-09-22 18:01 ` bugzilla-daemon
2010-09-22 18:11 ` bugzilla-daemon
2010-09-22 18:13 ` bugzilla-daemon
2010-09-27 19:26 ` bugzilla-daemon
2010-10-02 16:42 ` bugzilla-daemon
2010-10-11 20:43 ` Andreas Dilger
2010-10-04 18:48 ` bugzilla-daemon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.