From: Jens Axboe <jens.axboe@oracle.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops while booting 2.6.34-rc0 (block pull busted)
Date: Tue, 2 Mar 2010 08:56:56 +0100 [thread overview]
Message-ID: <20100302075656.GO5768@kernel.dk> (raw)
In-Reply-To: <201003011615.31709.dmitry.torokhov@gmail.com>
On Mon, Mar 01 2010, Dmitry Torokhov wrote:
> Hi,
>
> It looks like block tree that has been pulled today into mainline is
> busted, I am getting the Opps below on boot with the following commit:
>
> commit b1bf9368407ae7e89d8a005bb40beb70a41df539
> Merge: 524df55 4671a13
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Mon Mar 1 09:00:29 2010 -0800
>
> Merge branch 'for-2.6.34' of git://git.kernel.dk/linux-2.6-block
>
>
> but not with the previous one:
>
> commit 524df55725217b13d5a232fb5badb5846418ea0e
> Merge: 0f45339 6679ee1
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Mon Mar 1 08:58:44 2010 -0800
>
> Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6
>
> This is on plain Fedora 12 VM.
>
> Thanks.
>
> --
> Dmitry
>
> sd 2:0:0:0: Attached scsi generic sg1 type 0
> sd 2:0:0:0: [sda] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB)
> sd 2:0:0:0: [sda] Write Protect is off
> sd 2:0:0:0: [sda] Cache data unavailable
> sd 2:0:0:0: [sda] Assuming drive cache: write through
> sd 2:0:0:0: [sda] Cache data unavailable
> sd 2:0:0:0: [sda] Assuming drive cache: write through
> sda: sda1 sda2
> sd 2:0:0:0: [sda] Cache data unavailable
> sd 2:0:0:0: [sda] Assuming drive cache: write through
> sd 2:0:0:0: [sda] Attached SCSI disk
> device-mapper: multipath: version 1.1.1 loaded
> dracut: Scanning devices sda2 for LVM volume groups
> dracut: Reading all physical volumes. This may take a while...
> dracut: Found volume group "VolGroup" using metadata type lvm2
> dracut: 2 logical volume(s) in volume group "VolGroup" now active
> EXT4-fs (dm-0): mounted filesystem with ordered data mode
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [<ffffffff81128ee1>] mpage_end_io_read+0x45/0x6f
> PGD 3b776067 PUD 3b7b1067 PMD 0
> Oops: 0002 [#1] SMP
> last sysfs file: /sys/kernel/uevent_seqnum
> CPU 0
> Modules linked in: dm_multipath mptspi mptscsih mptbase scsi_transport_spi floppy [last unloaded: scsi_wait_scan]
>
> Pid: 1, comm: init Not tainted 2.6.33 #4 440BX Desktop Reference Platform/VMware Virtual Platform
> RIP: 0010:[<ffffffff81128ee1>] [<ffffffff81128ee1>] mpage_end_io_read+0x45/0x6f
Can you check where that is? Just do a gdb vmlinux and then an
l *mpage_end_io_read+0x45
--
Jens Axboe
next prev parent reply other threads:[~2010-03-02 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 0:15 Oops while booting 2.6.34-rc0 (block pull busted) Dmitry Torokhov
2010-03-02 7:56 ` Jens Axboe [this message]
2010-03-02 8:15 ` Jens Axboe
2010-03-02 8:39 ` Jens Axboe
2010-03-02 9:35 ` Dmitry Torokhov
2010-03-02 22:51 ` Dmitry Torokhov
2010-03-03 7:31 ` Jens Axboe
2010-03-02 10:13 ` walt
2010-03-02 16:50 ` Michael Breuer
2010-03-02 17:42 ` Steven Rostedt
2010-03-02 17:49 ` Steven Rostedt
2010-03-02 18:21 ` [GIT PULL] single block IO revert (Was "Re: Oops while booting 2.6.34-rc0 (block pull busted)") Jens Axboe
2010-03-02 19:17 ` Steven Rostedt
2010-03-02 19:21 ` 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=20100302075656.GO5768@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--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