Re: XFree86 seems to be being wrongly accused of doing the wrong thing

[Christian Guggenberger]

On 18.03.2004   08:57 Peter Williams wrote:
> Christian Guggenberger wrote:
> > On Thu, 2004-03-18 at 08:08, Peter Williams wrote:
> >
> > > Christian Guggenberger wrote:
> > >
> > > > > With 2.6.4 I'm getting the following messages very early in the boot 
> > > > > long before XFree86 is started:
> > > > >
> > > > > Mar 18 16:05:31 mudlark kernel: atkbd.c: Unknown key released 
> > > > > (translated set 2, code 0x7a on isa0060/serio0).
> > > > > Mar 18 16:05:31 mudlark kernel: atkbd.c: This is an XFree86 bug. It 
> > > > > shouldn't access hardware directly.
> > > > >
> > > > > They are repeated 6 times and are NOT the result of any keys being 
> > > > > pressed or released.
> > > >
> > > >
> > > > this has been fixed in XFree86 HEAD (4.4.99.1)
> > > > see changelog entry nr. 6 - the changes can easily be backported to 
> > > > 4.3.0, and work as expected on my box.
> > > > (no noise anymore)
> > >
> > > I repeat.  These messages are appearing when XFree86 is NOT running so 
> > > there is no way that it can be the cause of them.
> >
> >
> > yeah, sorry. After reading your previous mail I realized it, too.
> > If you have some spare time, you could boot with init=/bin/bash and then
> > start every boot script step by step to see which one is causing these
> > kernel messages.
>
> OK.  As requested, I just did a boot with init=/bin/bash and the bad news is 
> that the messages appeared before bash started.  So I think that confirms my 
> suspicion that they occur before any of the start scripts are invoked?
[cc'ed linux-kernel again]

Yeah, I do think so.



-
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/