Re: 2.4.17 & kbdrate

[Geert U. <ge...@li...>]

On Fri, 22 Mar 2002, Reinhard Nissl wrote:
> Geert Uytterhoeven wrote:
> > On Thu, 21 Mar 2002, Reinhard Nissl wrote:
> > > Geert Uytterhoeven wrote:
> > > > On Sun, 17 Mar 2002, Reinhard Nissl wrote:
> > > > > has anyone an idea, why "kbdrate" crashes?
> > > > >
> > > > > My config:
> > > > > SuSE Linux PPC 7.1
> > > > > 2.4.17 (cvs) kernel
> > > > >
> > > > > BTW: "kbdrate" doesn't crash with a good old 2.2.10 kernel.
> > > >
> > > > > Oops: kernel access of bad area, sig: 11
> > > > > NIP: C00989F0 XER: 00000000 LR: C0035E7C SP: C2DFFF20 REGS: c2dffe70 TRAP: 0300    Not tainted
> > > >        ^^^^^^^^
> > >
> > > read_port
> > 
> > APUS doesn't have the I/O ports of the PC keyboard controller.
> 
> But it's possible to open /dev/port. Would it be ok to disable this device on
> APUS, m68k, etc.?

On m68k it's disabled, except if CONFIG_ISA=y.
On APUS, it's valid if you have a PCI bridge, though.

> On the other hand: what's wrong in seeking beyond EOF?

Sorry, I don't understand what you mean here.

> > > It seems, that one (e. g. the first) of the lseek() calls in kbdrate.c
> > > (attached) trigger the problem.
> > 
> > Kbdrate should use the ioctls on m68k and APUS, because Amigas don't have PC
> > keyboard controllers.
> > 
> > Probably the ioctls are disabled in the kernel, or in the kbdrate.c program.
> 
> The same kbdrate binary works properly with a 2.2.10 kernel, so it must be a
> kernel issue. drivers/char/vt.c contains a case statement with the constant
> KDKBDREP, that kbdrate.c uses too, but I don't see any #ifdef/#endif
> statements, that would exclude this case statement.
> 
> I'll try some printk's soon.

OK.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds