From: "Ted Ts'o" <tytso@mit.edu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Florian Mickler <florian@mickler.org>,
Christian Casteyde <casteyde.christian@free.fr>
Subject: Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
Date: Sat, 2 Oct 2010 12:52:15 -0400 [thread overview]
Message-ID: <20101002165215.GK21129@thunk.org> (raw)
In-Reply-To: <sQALkqF1FWE.A.IiE.Qp6nMB@chimera>
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
WARNING: multiple messages have this Message-ID (diff)
From: Ted Ts'o <tytso-3s7WtUTddSA@public.gmane.org>
To: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
Cc: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Maciej Rutecki
<maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Florian Mickler <florian-sVu6HhrpSfRAfugRpC6u6w@public.gmane.org>,
Christian Casteyde
<casteyde.christian-GANU6spQydw@public.gmane.org>
Subject: Re: [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
Date: Sat, 2 Oct 2010 12:52:15 -0400 [thread overview]
Message-ID: <20101002165215.GK21129@thunk.org> (raw)
In-Reply-To: <sQALkqF1FWE.A.IiE.Qp6nMB@chimera>
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
next prev parent reply other threads:[~2010-10-02 16:52 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101002165215.GK21129@thunk.org \
--to=tytso@mit.edu \
--cc=casteyde.christian@free.fr \
--cc=florian@mickler.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.