From: Marc MERLIN <marc@merlins.org>
To: Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fairly reproduceable crash in 3.7.1 Null pointer rb_erase+0xc4/0x292
Date: Wed, 2 Jan 2013 15:01:28 -0800 [thread overview]
Message-ID: <20130102230128.GE8631@merlins.org> (raw)
In-Reply-To: <20130102222757.GC8631@merlins.org>
On Wed, Jan 02, 2013 at 02:27:57PM -0800, Marc MERLIN wrote:
> Google only shows hits pointing to an ext4 patch that didn't go in 3.7
> proper.
>
> http://marc.merlins.org/tmp/crash.jpg
Grumble, I kind of forgot to add the link to my .config, sorry about
that:
http://marc.merlins.org/tmp/.config-3.7.1-amd64-preempt-20121226
While my crash picture is lame (sorry), I'm happy to provide what else I
can before I go home and can provide a proper serial console crash dump.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2013-01-02 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 22:27 Fairly reproduceable crash in 3.7.1 Null pointer rb_erase+0xc4/0x292 Marc MERLIN
2013-01-02 23:01 ` Marc MERLIN [this message]
2013-01-03 7:12 ` Romain Francoise
2013-01-03 8:42 ` Marc MERLIN
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=20130102230128.GE8631@merlins.org \
--to=marc@merlins.org \
--cc=linux-kernel@vger.kernel.org \
/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