From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [GIT PULL] Core block IO bits for 2.6.39 - early Oops
Date: Thu, 24 Mar 2011 20:34:41 +0100 [thread overview]
Message-ID: <20110324193441.GA1723@gentoo.trippels.de> (raw)
In-Reply-To: <4D8B9457.2020608@fusionio.com>
On 2011.03.24 at 19:58 +0100, Jens Axboe wrote:
> On 2011-03-24 19:54, Markus Trippelsdorf wrote:
> > On 2011.03.24 at 19:51 +0100, Jens Axboe wrote:
> >> On 2011-03-24 19:36, Jens Axboe wrote:
> >>> On 2011-03-24 19:30, Markus Trippelsdorf wrote:
> >>>> On 2011.03.24 at 14:43 +0100, Jens Axboe wrote:
> >>>>>
> >>>>> This is the main pull request for the block IO layer and friends for
> >>>>> 2.6.39.
> >>>>
> >>>> This merge results in an early oops on my system (amd64, xfs).
> >>>> See the attached photo.
> >>>>
> >>>
> >>> Auch. Can you ensure that you have CONFIG_DEBUGINFO=y in your .config
> >>> and then do:
> >>>
> >>> $ gdb vmlinux
> >>> ...
> >>> l *cfq_insert_request+0x32
> >>>
> >>> and send that output?
> >>
> >> I took a closer look at the oops, and it most likely looks like q ==
> >> NULL (offset 0x18 == q->elevator). You left out the Code part, so I
> >> can't verify that for certain. Which makes very little sense. I take it
> >> this is 100% reproducible? When you send the gdb output, please also
> >> attach your .config.
> >
> > Yes, it's 100% reproducible here. My .config follows:
>
> Can you try this patch and see if it makes a difference?
There's no patch ;-)
> If you boot without the patch and add elevator=noop, does it then work?
It works insofar as the Oops is gone. But my xfs partitions apparently
still get corrupted (I had to run xfs_repair on several of them, because
they would not mount otherwise).
--
Markus
next prev parent reply other threads:[~2011-03-24 19:34 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 13:43 [GIT PULL] Core block IO bits for 2.6.39 Jens Axboe
2011-03-24 18:30 ` [GIT PULL] Core block IO bits for 2.6.39 - early Oops Markus Trippelsdorf
2011-03-24 18:36 ` Jens Axboe
2011-03-24 18:47 ` Markus Trippelsdorf
2011-03-24 18:51 ` Jens Axboe
2011-03-24 18:54 ` Markus Trippelsdorf
2011-03-24 18:58 ` Jens Axboe
2011-03-24 19:34 ` Markus Trippelsdorf [this message]
2011-03-24 19:36 ` Jens Axboe
2011-03-24 19:45 ` Markus Trippelsdorf
2011-03-24 19:57 ` Jens Axboe
2011-03-24 20:06 ` Markus Trippelsdorf
2011-03-24 21:01 ` Jens Axboe
2011-03-24 21:41 ` Markus Trippelsdorf
2011-03-25 7:23 ` Jens Axboe
2011-03-25 8:37 ` Markus Trippelsdorf
2011-03-25 8:44 ` Jens Axboe
2011-03-25 9:27 ` Markus Trippelsdorf
2011-03-25 9:57 ` Markus Trippelsdorf
2011-03-25 10:11 ` Jens Axboe
2011-03-25 12:44 ` Jens Axboe
2011-03-25 13:09 ` Markus Trippelsdorf
2011-03-25 14:10 ` Jens Axboe
2011-03-25 14:14 ` Markus Trippelsdorf
2011-03-25 14:18 ` Chris Mason
2011-03-25 14:19 ` Chris Mason
2011-03-25 14:24 ` Markus Trippelsdorf
2011-03-25 14:20 ` Jens Axboe
2011-03-25 14:28 ` Markus Trippelsdorf
2011-03-25 15:51 ` Jens Axboe
2011-03-25 15:58 ` Markus Trippelsdorf
2011-03-25 16:01 ` Jens Axboe
2011-03-24 22:06 ` Markus Trippelsdorf
2011-03-25 4:41 ` Dave Chinner
2011-03-25 7:26 ` Jens Axboe
2011-03-25 11:59 ` Theodore Tso
2011-03-25 12:14 ` Jens Axboe
2011-03-25 12:33 ` Ted Ts'o
2011-03-25 12:43 ` Jens Axboe
2011-03-25 13:01 ` Chris Mason
2011-03-25 21:35 ` [GIT PULL] Core block IO bits for 2.6.39 Geert Uytterhoeven
2011-03-26 6:29 ` Jens Axboe
2011-03-26 7:21 ` Geert Uytterhoeven
2011-03-26 8:25 ` Jens Axboe
2011-03-26 8:34 ` Geert Uytterhoeven
2011-03-26 9:26 ` Jens Axboe
2011-03-26 16:48 ` Linus Torvalds
2011-03-26 16:53 ` Jens Axboe
2011-03-26 18:48 ` Jens Axboe
2011-03-27 13:21 ` Alan Cox
2011-03-27 11:49 ` Avi Kivity
2011-03-27 12:00 ` Jens Axboe
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=20110324193441.GA1723@gentoo.trippels.de \
--to=markus@trippelsdorf.de \
--cc=chris.mason@oracle.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome