From: Arjan van de Ven <arjan@infradead.org>
To: peterz@infradeads.org
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Upcoming oops in lockdep
Date: Sat, 23 Aug 2008 13:49:55 -0700 [thread overview]
Message-ID: <20080823134955.07096e34@infradead.org> (raw)
in kerneloops.org a crash (slab poison) in mark_lock is coming up
rapidly:
http://www.kerneloops.org/searchweek.php?search=mark_lock
and despite a few earlier hits on the same function it seems to be
something introduced in 2.6.27-rc... (the older ones aren't slab poison)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next reply other threads:[~2008-08-23 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 20:49 Arjan van de Ven [this message]
2008-08-25 6:51 ` Upcoming oops in lockdep Peter Zijlstra
2008-08-25 6:54 ` Peter Zijlstra
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=20080823134955.07096e34@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradeads.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox