Skip to contentSkip to conversation

Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open

DISCUSSION Martin J. Bligh 3 participants 4 messages Mar 11, 2003 – Mar 12, 2003 Char and misc drivers

lore
Share & tools
lore
#0 lore raw

I'm getting lots of these messages whilst running big SDET runs on an 16-way machine ... anyone recognize them?
(64-bk3 + a few patches).

dev (pts(136,0)) tty->count(4) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(4) != #fd's(3) in tty_open
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in release_dev
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(6) != #fd's(5) in tty_open
Warning: dev (pts(136,0)) tty->count(7) != #fd's(6) in tty_open
Warning: dev (pts(136,0)) tty->count(8) != #fd's(7) in tty_open
Warning: dev (pts(136,0)) tty->count(9) != #fd's(8) in tty_open
Warning: dev (pts(136,0)) tty->count(10) != #fd's(9) in tty_open
Warning: dev (pts(136,0)) tty->count(11) != #fd's(10) in tty_open
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in tty_open
Warning: dev (pts(136,0)) tty->count(13) != #fd's(12) in tty_open
Warning: dev (pts(136,0)) tty->count(14) != #fd's(13) in tty_open
Warning: dev (pts(136,0)) tty->count(15) != #fd's(14) in tty_open
Warning: dev (pts(136,0)) tty->count(16) != #fd's(15) in tty_open
Warning: dev (pts(136,0)) tty->count(17) != #fd's(16) in tty_open
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in tty_open
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in release_dev
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in tty_open
Warning: dev (pts(136,0)) tty->count(19) != #fd's(18) in tty_open
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in tty_open
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in release_dev
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in release_dev
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in release_dev
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in release_dev
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in tty_open
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in release_dev
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in release_dev
Warning: dev (pts(136,0)) tty->count(19) != #fd's(18) in release_dev
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in release_dev
Warning: dev (pts(136,0)) tty->count(17) != #fd's(16) in release_dev
Warning: dev (pts(136,0)) tty->count(16) != #fd's(15) in release_dev
Warning: dev (pts(136,0)) tty->count(15) != #fd's(14) in release_dev
Warning: dev (pts(136,0)) tty->count(14) != #fd's(13) in release_dev
Warning: dev (pts(136,0)) tty->count(13) != #fd's(12) in release_dev
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in release_dev
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in tty_open
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in release_dev
Warning: dev (pts(136,0)) tty->count(11) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(10) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(9) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(9) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(9) != #fd's(4) in release_dev
Warning: dev (pts(136,0)) tty->count(9) != #fd's(5) in tty_open
Warning: dev (pts(136,0)) tty->count(10) != #fd's(6) in tty_open
Warning: dev (pts(136,0)) tty->count(11) != #fd's(7) in tty_open

#1 lore raw
Quoted 8 lines · Martin J. Bligh

I'm getting lots of these messages whilst running big SDET runs on an 16-way machine ... anyone recognize them?
(64-bk3 + a few patches).

dev (pts(136,0)) tty->count(4) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(4) != #fd's(3) in tty_open
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in release_dev

These are some of the things I saw when reporting the tty races and doing zillions of open/closes on pty/tty pairs. The tty layer has some fun code dealing with open v close v hangup v vhangup

#2 lore raw
In reply to Martin J. Bligh
Quoted 6 lines · Martin J. Bligh

I'm getting lots of these messages whilst running big SDET runs on an 16-way machine ... anyone recognize them?
(64-bk3 + a few patches).

dev (pts(136,0)) tty->count(4) != #fd's(3) in release_dev

The file_list_lock patches affect this. Do you have those applied?

If so, and if it is repeatable, this might help. (Unlikely, but it might).

drivers/char/tty_io.c renamed from drivers/char/tty_io.c~tty_files-fixes +4 -0
diff -puN drivers/char/tty_io.c~tty_files-fixes drivers/char/tty_io.c
@@ -1037,7 +1037,9 @@ static void release_mem(struct tty_struc
 		}
 		o_tty->magic = 0;
 		(*o_tty->driver.refcount)--;
+		file_list_lock();
 		list_del(&o_tty->tty_files);
+		file_list_unlock();
 		free_tty_struct(o_tty);
 	}
 
@@ -1049,7 +1051,9 @@ static void release_mem(struct tty_struc
 	}
 	tty->magic = 0;
 	(*tty->driver.refcount)--;
+	file_list_lock();
 	list_del(&tty->tty_files);
+	file_list_unlock();
 	module_put(tty->driver.owner);
 	free_tty_struct(tty);
 }

_

#3 lore raw
Quoted 7 lines
Quoted 5 lines

I'm getting lots of these messages whilst running big SDET runs on an 16-way machine ... anyone recognize them?
(64-bk3 + a few patches).

dev (pts(136,0)) tty->count(4) != #fd's(3) in release_dev

The file_list_lock patches affect this. Do you have those applied?

Yes, sorry ... was running out the door, crap description ;-)

Quoted 1 line

If so, and if it is repeatable, this might help. (Unlikely, but it might).

Mmm ... OK. will try that. Thanks,

M.