From: David Miller <davem@davemloft.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ext3 oops on shutdown
Date: Wed, 25 Oct 2006 00:51:34 -0700 (PDT) [thread overview]
Message-ID: <20061025.005134.74748405.davem@davemloft.net> (raw)
In-Reply-To: <20061024.175751.07640578.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Tue, 24 Oct 2006 17:57:51 -0700 (PDT)
> I just started to see the following ext3 umount() oops on
> shutdown, it happens every shutdown, has anyone else seen
> it?
>
> I'll start bisecting soon... this was on sparc64.
>
> free_block()+0x50/0x190
> cache_flusharray()+0x74/0xa0
> kmem_cache_free()
> journal_destroy_revoke()
> journal_destroy()
> ext3_put_super()
> generic_shutdown_super()
> kill_block_super()
> deactivate_super()
> sys_umount()
Just as an FYI, I bisected it down to this commit:
commit 6b4b78fed47e7380dfe9280b154e8b9bfcd4c86c
Author: Matt Domsch <Matt_Domsch@dell.com>
Date: Fri Sep 29 15:23:23 2006 -0500
PCI: optionally sort device lists breadth-first
which makes no sense. Effectively all this changeset does is add some
__init section code to the PCI layer which never gets executed on
non-i386. And even on i386 it only runs if you give a special kernel
command line option.
So the only side effect of this code for sparc64, by checking the
System.map before/after this change, is to move the __init_end ahead
by 1 PAGE_SIZE.
It's probably some sparc64 issue, maybe even some error wrt. freeing
up init memory. I'll try to track it down. I'm actually quite
curious what this bug is :-)
next prev parent reply other threads:[~2006-10-25 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 0:57 David Miller
2006-10-25 7:51 ` David Miller [this message]
2006-10-26 6:06 ` David Miller
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=20061025.005134.74748405.davem@davemloft.net \
--to=davem@davemloft.net \
--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
Powered by JetHome