[lkml]   [2003]   [Oct]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.0-test8-mm1 wrote:
> On Mon, 20 Oct 2003 17:27:32 PDT, Andrew Morton said:
> > 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_FONT_8x16=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 (, 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:58    [W:0.085 / U:9.452 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site