From: David Miller <[email protected]>
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 <[email protected]>
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 :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
