lkml.org 
[lkml]   [2002]   [Jan]   [7]   [last100]   RSS Feed
Views: [more markup]   [less markup]   [headers]   [forward]  
 
Messages in this thread
/
DateSun, 06 Jan 2002 23:20:22 -0800
FromAndrew Morton <>
SubjectRe: Serial Driver Name Question (kernels 2.4.x)
Richard Gooch wrote:
> 
> > > Why exactly is just "ttyS" broken?
> >
> > umm..  Because it doesn't tell the user which serial port the
> > message pertains to?
> 
> Exactly where is it broken? I look at my dmesg output and things look
> fine.
> 

Try disabling devfs.

At the head-of-thread, Ivan said:


> This was spotted by a Cyclades customer who was getting overrun msgs
> as:
> 
> ttyC: 1 input overrun(s)
> 
> After he changed the driver.name to be "ttyC%d", he started to get
> properly formatted msgs, such as:
> 
> ttyC39: 1 input overrun(s)
> 
> This problem would happen on any msg that used the function
> tty_name() to get the TTY name, and after the change the problem
> disappeared completely.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 11:15    [W:0.423 / U:0.080 seconds]
©2003-2008 Jasper Spaans