On Sat, Aug 27, 2005 at 08:12:47PM +1000, Rod Butcher wrote: > Greetings, my first post here. I have been compiling my own kernels for > a year now with no problems, but now I am getting a strange problem with > 2.6.13.rc3 with mm patches > :- > information about the data going thru my eth1, which is a USB connection > to my Motorola internet cable modem, seems to be "leaking" into the > linux console display - e.g. if I am doing something in the native > console (i.e. not under X) , at random large chunks of stuff like this :- > > Aug 27 20:02:43 localhost kernel: Inbound IN=eth1 OUT= > MAC=00:12:c9:4c:17:65:00:05:9a:d5:88:70:08:00 SRC=61.47.147.92 > DST=211.30.153.231 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=58134 DF > PROTO=TCP SPT=3015 DPT=4899 WINDOW=64800 RES=0x00 SYN URGP=0 > > gets displayed on the console for a few seconds. Looks like a LOG target from iptables. > Now - this seems to be exactly the stuff that should only go to syslog, > isn't it ? No, depends on the log level of the message and from what log level the kernel displays it on the console. > Also, I find that the command dmesg displays similar rubbish - I > understand it should display bootup info about loaded modules ? No, dmesg displays the contents of the kernel log buffer. As this is a ring buffer, later messages will overwrite the earlier ones. If you have enought other messages, the boot messages will be overwritten. Most distributions dump the boot messages to a file in /var/log/ (boot.msg, dmesg, or similar file). > I realize this is a beta kernel, but I'd really like to understand more > about what's going on internally when things go wrong. AFAICS nothing is wrong. Erik -- Erik Mouw J.A.K.Mouw@xxxxxxxxxxxxxx mouw@xxxxxxxxxxxx
Attachment:
signature.asc
Description: Digital signature
