Kern.log and sys.log filling up!

Darcy Roberts darcy_ro at msn.com
Sun Jan 28 11:35:06 PST 2007


OK:

I've finally finished and have a booting LFS 6.2 system.

I've enabled a bunch of stuff in the kernel and it all seems to work ok.

I've got two serial ports on the MB (ttyS0 and ttyS1), four more on the PCI
bus (ttyS4, ttyS5, ttyS6 and ttyS7)
These all appear to work. I can send output to any of the ports.

The problem is that /var/log/kern.log and /var/log/sys.log are filling up at
the rate of about 1K per second with messages such as:

Jan 28 09:17:33 test kernel: evbug.c: Event. Dev: isa0060/serio0/input0,
Type: 0, Code: 0, Value: 0
Jan 28 09:17:33 test kernel: evbug.c: Event. Dev: isa0060/serio0/input0,
Type: 4, Code: 4, Value: 28
Jan 28 09:17:33 test kernel: evbug.c: Event. Dev: isa0060/serio0/input0,
Type: 1, Code: 28, Value: 1
Jan 28 09:17:33 test kernel: evbug.c: Event. Dev: isa0060/serio0/input0,
Type: 0, Code: 0, Value: 0

The Code and the Value values are all over the place.

I've redirected output to /dev/ttyS0 and it seems to work.

I've disabled serial console support, interrupt sharing for serial.

In the kernel.log, I can see the following:

.. Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
.. Serial8250: ttyS0 at I/O 0x3f8 (irq=4) is a 16550A
.. Serial8250: ttyS0 at I/O 0x2f8 (irq=3) is a 16550A
.. Serial8250: ttyS0 at I/O 0x3f8 (irq=0) is a 16550A
.. Serial8250: ttyS0 at I/O 0x2f8 (irq=0) is a 16550A
.. 00:06 ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
.. 00:07 ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

It then goes on to discover the PCI UARTS.

What kernel config have I messed up?

Regards,
Darcy Roberts
AICDairy.com




More information about the lfs-support mailing list