[lkml]   [2004]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.9-rc2-mm3
On Fri, 2004-09-24 at 11:16, James Morris wrote:
> On Fri, 24 Sep 2004, James Morris wrote:
> > I'm getting what looks like a deadlock during boot with this kernel,
> > .config, bootlog and sysrq output attached. Looks like it may be related
> > to the serial/tty code?
> Backing these out lets me boot again:
> +tty-driver-take-4-try-2.patch
> +tty-locking-build-fix.patch
> [<c026b3a4>] tty_termios_baud_rate+0x11/0x67
> [<c027f485>] uart_get_baud_rate+0x53/0xd4
> [<c0283af1>] serial8250_set_termios+0x8d/0x348
> [<c027f580>] uart_change_speed+0x4a/0x64
> [<c0280664>] uart_set_termios+0x4f/0x162
> [<c026e94f>] change_termios+0x1b3/0x21a
> [<c026ea40>] set_termios+0x8a/0xf9
> [<c026ad15>] tty_ioctl+0x152/0x44f
> [<c0169687>] sys_ioctl+0x231/0x282
> [<c0105d09>] sysenter_past_esp+0x52/0x71

I am seeing this deadlock also.

tty_termios_lock is acquired in change_termios(), tty_ioctl.c

change_termios() calls the driver set_termios callback
which in turn calls tty_termios_baud_rate(), tty_io.c
which tries to acquire the lock again.

Paul Fulghum

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:06    [W:0.084 / U:2.392 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site