lkml.org 
[lkml]   [1996]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subjectprintk doesn't handle tabs
Date
Sometimes I get this message on the console (BTW, is this normal or
something to worry about?):

IPX: Network number collision a993
oeth0 802.3 and eth0 802.2
^
The 'o' on the second line is not really 'o' but it's the character
with the code 8 from the PC character set (a small circle). This
message contains a tab and printk() doesn't seem to handle that.
It's in linux/net/ipx/af_ipx.c. It might be a good idea to search
for other printk's trying to use tabs and use spaces instead, or
modify printk to expand tabs to spaces.

The machine is on a large network with several Netware servers.
IPX is configured with auto primary on and auto interface on.

Marek


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.029 / U:5.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site