[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

2.6.36-rc3-git5: Reported regressions from 2.6.35

[Rafael J. Wysocki]

[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-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2010-09-02 18:55 (11 days old)
Message-ID	: <20100902145509.28e4f998-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
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-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org>
Date		: 2010-09-01 6:37 (12 days old)
Message-ID	: <tkrat.ed8eda6bc8ffe64e-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org>
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-VsYtu1Qij5c@public.gmane.org>
Date		: 2010-08-31 20:14 (13 days old)
Message-ID	: <201008312214.52473.thomas-VsYtu1Qij5c@public.gmane.org>
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-GANU6spQydw@public.gmane.org>
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-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2010-08-27 12:35 (17 days old)
Message-ID	: <2136707099.1405541282912500148.JavaMail.root-k5qu2F3t005+R5eDjrG6zsCp5Q1pQRjfhaY/URYTgi6ny3qCrzbmXA@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128291252612135&w=2
Handled-By	: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17331
Subject		: BUG: scheduling while atomic
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-27 7:59 (17 days old)
Message-ID	: <20100827075911.GA5966-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>
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-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Date		: 2010-08-27 20:04 (17 days old)
Message-ID	: <4C781A3A.4010707-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-27 1:56 (17 days old)
First-Bad-Commit: http://git.kernel.org/linus/5a652052fedbd7869572c757dd2ffc2ed420c69d
Message-ID	: <AANLkTinHbEW36D5R9NSrGgfbOC0Hri3Tg-fA0iR92Udi-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128287422106267&w=2
Handled-By	: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17131
Subject		: WARN with 3c905 boomerang NIC
Submitter	: Doug Nazar <nazard.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-22 6:35 (22 days old)
Message-ID	: <4C70C516.5020404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128245894300623&w=2
Handled-By	: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.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-+ZI9xUNit7I@public.gmane.org>
Date		: 2010-08-21 15:24 (23 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 (25 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=16961
Subject		: kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-19 9:54 (25 days old)
Message-ID	: <<20100819095429.GA5201-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=128221169606214&w=2
Handled-By	: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>


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 (26 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=17742
Subject		: 2.6.36-rc2-git5: Oops in snd_pcm_substream_proc_status_read()
Submitter	: Chuck Ebbert <cebbert-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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-l3A5Bk7waGM@public.gmane.org>
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!

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

2.6.36-rc3-git5: Reported regressions from 2.6.35

[Rafael J. Wysocki]

[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!

[Bug #16951] hackbench regression with 2.6.36-rc1

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16951
Subject		: hackbench regression with 2.6.36-rc1
Submitter	: Zhang, Yanmin <yanmin_zhang-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Date		: 2010-08-18 6:18 (26 days old)
Message-ID	: <1282112318.21202.8.camel-sz7BYL/Y5Hu/P+R7jlPCFVaTQe2KTcn/@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128211235904910&w=2

[Bug #16951] hackbench regression with 2.6.36-rc1

[Rafael J. Wysocki]

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

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


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

[Bug #16961] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16961
Subject		: kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-19 9:54 (25 days old)
Message-ID	: <<20100819095429.GA5201-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>
References	: http://marc.info/?l=linux-kernel&m=128221169606214&w=2
Handled-By	: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16971
Subject		: qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
Submitter	: Meelis Roos <mroos-Y27EyoLml9s@public.gmane.org>
Date		: 2010-08-19 21:03 (25 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 #17061] 2.6.36-rc1 on zaurus: bluetooth regression

[Rafael J. Wysocki]

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

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


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

[Bug #17131] WARN with 3c905 boomerang NIC

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17131
Subject		: WARN with 3c905 boomerang NIC
Submitter	: Doug Nazar <nazard.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-22 6:35 (22 days old)
Message-ID	: <4C70C516.5020404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128245894300623&w=2
Handled-By	: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

[Bug #16961] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16971
Subject		: qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq
Submitter	: Meelis Roos <mroos@linux.ee>
Date		: 2010-08-19 21:03 (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 #17131] WARN with 3c905 boomerang NIC

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #17311] 2.6.36-rc2-git4 - INFO: possible circular locking dependency detected

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #17321] i386 WARNING: at kernel/softirq.c:143 _local_bh_enable_ip+0x2f/0x7e

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #17341] kdump regression compared to v2.6.35

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #17331] BUG: scheduling while atomic

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17331
Subject		: BUG: scheduling while atomic
Submitter	: Sergey Senozhatsky <sergey.senozhatsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2010-08-27 7:59 (17 days old)
Message-ID	: <20100827075911.GA5966-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128289602925505&w=2

[Bug #17331] BUG: scheduling while atomic

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #17742] 2.6.36-rc2-git5: Oops in snd_pcm_substream_proc_status_read()

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17742
Subject		: 2.6.36-rc2-git5: Oops in snd_pcm_substream_proc_status_read()
Submitter	: Chuck Ebbert <cebbert-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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-l3A5Bk7waGM@public.gmane.org>
Patch		: http://mailman.alsa-project.org/pipermail/alsa-devel/2010-September/031275.html

[Bug #17752] 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17752
Subject		: 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)
Submitter	: Stefan Richter <stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org>
Date		: 2010-09-01 6:37 (12 days old)
Message-ID	: <tkrat.ed8eda6bc8ffe64e-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128332308528119&w=2

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

[Bug #17752] 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 #17742] 2.6.36-rc2-git5: Oops in snd_pcm_substream_proc_status_read()

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


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

[Bug #17952] bdi-default hung waiting for kthread_stop to finish

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17952
Subject		: bdi-default hung waiting for kthread_stop to finish
Submitter	: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2010-09-02 18:55 (11 days old)
Message-ID	: <20100902145509.28e4f998-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
References	: http://marc.info/?l=linux-kernel&m=128345371904504&w=2

[Bug #17952] bdi-default hung waiting for kthread_stop to finish

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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

Re: [Bug #17131] WARN with 3c905 boomerang NIC

[David Miller]

From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Date: Sun, 12 Sep 2010 20:14:27 +0200 (CEST)

> 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=17131
> Subject		: WARN with 3c905 boomerang NIC
> Submitter	: Doug Nazar <nazard.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-08-22 6:35 (22 days old)
> Message-ID	: <4C70C516.5020404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> References	: http://marc.info/?l=linux-kernel&m=128245894300623&w=2
> Handled-By	: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

Paul, could you please get the softirq.c _local_bh_enable_ip() warning
patch referenced in that bugzilla queued up for Linus's tree if you
haven't done so already?  I'm pretty sure I ACK'd it too, thanks :-)

Re: [Bug #17131] WARN with 3c905 boomerang NIC

[David Miller]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Sun, 12 Sep 2010 20:14:27 +0200 (CEST)

> 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=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>

Paul, could you please get the softirq.c _local_bh_enable_ip() warning
patch referenced in that bugzilla queued up for Linus's tree if you
haven't done so already?  I'm pretty sure I ACK'd it too, thanks :-)

Re: [Bug #16961] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978

[Sergey Senozhatsky]

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

On (09/12/10 20:14), Rafael J. Wysocki wrote:
> 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2010-08-19 9:54 (25 days old)
> Message-ID	: <<20100819095429.GA5201-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>
> References	: http://marc.info/?l=linux-kernel&m=128221169606214&w=2
> Handled-By	: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 
> 

Hello,
Fixed by
commit da908f2fb4e783c2a4de751fb90f11a0dd041161
Author: Zachary Amsden <zamsden-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>


	Sergey

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

Re: [Bug #16961] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978

[Sergey Senozhatsky]

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

On (09/12/10 20:14), Rafael J. Wysocki wrote:
> 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>
> 
> 

Hello,
Fixed by
commit da908f2fb4e783c2a4de751fb90f11a0dd041161
Author: Zachary Amsden <zamsden@redhat.com>


	Sergey

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

Re: [Bug #16961] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978

[Rafael J. Wysocki]

On Monday, September 13, 2010, Sergey Senozhatsky wrote:
> On (09/12/10 20:14), Rafael J. Wysocki wrote:
> > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2010-08-19 9:54 (25 days old)
> > Message-ID	: <<20100819095429.GA5201-dY8u8AhHFaWtd10JCjopabkcH5ONE+aC@public.gmane.org>>
> > References	: http://marc.info/?l=linux-kernel&m=128221169606214&w=2
> > Handled-By	: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > 
> > 
> 
> Hello,
> Fixed by
> commit da908f2fb4e783c2a4de751fb90f11a0dd041161
> Author: Zachary Amsden <zamsden-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Thanks, closing.

Rafael

Re: [Bug #16961] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:1978

[Rafael J. Wysocki]

On Monday, September 13, 2010, Sergey Senozhatsky wrote:
> On (09/12/10 20:14), Rafael J. Wysocki wrote:
> > 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>
> > 
> > 
> 
> Hello,
> Fixed by
> commit da908f2fb4e783c2a4de751fb90f11a0dd041161
> Author: Zachary Amsden <zamsden@redhat.com>

Thanks, closing.

Rafael

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


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

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


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

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


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

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

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

[Ted Ts'o]

On Sun, Sep 26, 2010 at 10:04:13PM +0200, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17361
> Subject		: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
> Submitter	: Christian Casteyde <casteyde.christian-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

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

[Ted Ts'o]

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

See my latest comment here:

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

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

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

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

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

					- Ted

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

[Vegard Nossum]

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

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

[Vegard Nossum]

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

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

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

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


Vegard

[Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[Rafael J. Wysocki]

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

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


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

[Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access

[bugzilla-daemon]

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.

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

[Andreas Dilger]

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