> On Sat, 8 Aug 1998, Gerd Knorr wrote:
>
> > On Fri, 7 Aug 1998, Alex Buell wrote:
> >
> > > > Next step ahead: vesafb uses the protected mode interface for palette
> > > > changes too.
> > >
> > > Does it only does this on initialisation?
> >
> > No, for all palette changes. This should make gfx boards which have not
> > the standard vga palette registers (MediaGX?) work with vesafb. Here is
> > the patch (against vanilla 2.1.115).
> >
> > Gerd
>
> This patch causes me major oopsing... I have a ksymoops'ed, and raw, and
> an strace of an offending zsh process that did it. Every time I tried to
> do a history search, it oopsed. Sometimes oopsed maniacally on shutdown.
What does vesafb say at startup?
> >>EIP: c018839f <write_chan+14f/1e8>
> Trace: c011bc4e <handle_mm_fault+c2/148>
> Trace: c0179839 <tty_write+10d/15c>
> Trace: c018839f <write_chan+14f/1e8>
> Trace: c0124f50 <sys_write+c0/124>
> Trace: c010a9c0 <system_call+34/38>
No fbcon here. Hmm, maybe the patch triggers some race in tty/console
code?
Gerd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html