Re: 2.6.0-test8-mm1

From: Andrew Morton
Date: Mon Oct 20 2003 - 20:58:02 EST


Valdis.Kletnieks@xxxxxx wrote:
>
> On Mon, 20 Oct 2003 17:27:32 PDT, Andrew Morton said:
> > Valdis.Kletnieks@xxxxxx wrote:
> > >
> > > This ring any bells? What you want tested? etc etc....
> >
> > Can you try disabling all fbdev stuff in config?
>
> OK.. That booted just fine, didn't hang in pty_init, didn't hit the
> WARN_ON added to fs_inoce.c.
>
> So we have:
>
> works:
> # CONFIG_FB is not set
>
> Doesn't work:
> CONFIG_FB=y
> CONFIG_FB_VESA=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_PCI_CONSOLE=y
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_MONO=y
> CONFIG_LOGO_LINUX_VGA16=y
> CONFIG_LOGO_LINUX_CLUT224=y
>
> I've not had a chance to play binary search on those options yet.. Graphics
> card is an NVidia GeForce 440Go, and was previous working just fine with
> framebuffer over on vc1-6 and NVidia's driver on an XFree86 on vc7. (OK, I
> admit I didn't stress test the framebuffer side much past "penguins and
> scroiled text"...)
>

Thanks. You're now the third person (schlicht@xxxxxxxxxxxxxxx,
jeremy@xxxxxxxx) who reports that the weird oopses (usually in
invalidate_list()) go away when the fbdev code is disabled.

You're using vesafb on nvidia, Jeremy is using vesafb on either radeon or
nvidia, not sure about Thomas.

Has anyone tried CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC, see if that
turns anything up?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/