Messages in this thread | | | Date | Tue, 10 Oct 2006 18:05:23 -0500 | Subject | Re: BUG() in copy_fdtable() with 64K pages (2.6.19-rc1-mm1) | From | (Linas Vepstas) |
| |
On Tue, Oct 10, 2006 at 01:31:11PM -0700, Vadim Lobanov wrote: > On Tuesday 10 October 2006 13:20, Linas Vepstas wrote: > > On Tue, Oct 10, 2006 at 12:15:19PM -0500, Olof Johansson wrote: > > > I keep hitting this on -rc1-mm1. The system comes up but I can't login > > > since login hits it. > > > > > > Bisect says that > > > fdtable-implement-new-pagesize-based-fdtable-allocator.patch is at fault. > > > > > > CONFIG_PPC_64K_PAGES=y is required for it to fail, with 4K pages it's > > > fine. > > > > > > (Hardware is a Quad G5, 1GB RAM, g5_defconfig + CONFIG_PPC_64K_PAGES, > > > defaults on all new options) > > > > > > kernel BUG in copy_fdtable at fs/file.c:138! > > > > FWIW, I too was hitting this bug, during init: > > > > [ 41.659823] Freeing unused kernel memory: 320k freed > > INIT: version 2.86 bootin[ 42.509322] kernel BUG in copy_fdtable at > > fs/file.c:138! > > > > and of course systm does not come up.
I forgot to mention my h/w was completely different (a cell)
> I'm digging through this right now, trying to figure out exactly what went > wrong (and why some people are seeing this, while others are not). All the > code seems correct; another pair of eyes is always welcome though.
The patch that AKPM just posted at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc1/2.6.19-rc1-mm1/hot-fixes/revert-fdtable-implement-new-pagesize-based-fdtable-allocator.patch
boots for me.
Thanks Andrew!
--linas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |