Hi Ray,<div><br><div class="gmail_quote">On Tue, Sep 28, 2010 at 7:41 PM, Ray Strode <span dir="ltr"><<a href="mailto:halfline@gmail.com">halfline@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<div class="im"><br>
On Mon, Sep 27, 2010 at 6:20 PM, Jerome Martin<br>
<<a href="mailto:jxm@risingtidesystems.com">jxm@risingtidesystems.com</a>> wrote:<br>
> Bingo, I never actually quit plymouth this explain why I did not get the<br>
> logs :-)<br>
> Please find the log file attached :-)<br>
<br>
</div>So, I'm seeing some strangeness in the fidelity of the logs. It seems<br>
like ply-logger may have a bug in it, which is unfortunate...<br>
<br>
Anyway, looking at the output, I see:<br>
<br>
[ 38.755306] [main.c]<br>
on_display_message:displaying message Running scripts in rcS.d/ took 4<br>
seconds.<br>
[...]<br>
[ 38.794012] [ply-terminal.c]<br>
on_tty_disconnected:tty disconnected (fd 10)<br>
[ 38.794015] [ply-terminal.c]<br>
on_tty_disconnected:trying to reopen terminal '/dev/tty1'<br>
[...]<br>
[ 38.794021] [./plugin.c]<br>
on_input_source_disconnected:input source disconnected, reopening<br>
<br>
So it looks like both parts of the code that are supposed to notice<br>
the tty going away, do it notice it going away, and then both parts<br>
reopen without any error messages.<br></blockquote><div><br></div><div><nod>, so you do get the hang up properly notified. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Can you post the output of<br>
<br>
sudo stty -a --file=/dev/tty1<br></blockquote><div><br></div><div><div>root@000c29af1815:~# stty -a --file=/dev/tty1</div><div>speed 38400 baud; rows 30; columns 80; line = 0;</div><div>intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z;</div>
<div>rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;</div><div>-parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts</div><div>-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel iutf8</div>
<div>opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0</div><div>isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke</div></div><div><br></div><div>And for reference, tty2 where my getty is:</div>
<div><div>speed 38400 baud; rows 30; columns 80; line = 0;</div><div>intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z;</div>
<div>rprnt = ^R; werase = ^W; lnext = <undef>; flush = ^O; min = 1; time = 0;</div><div>-parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts</div><div>-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl ixon ixoff -iuclc -ixany -imaxbel -iutf8</div>
<div>opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0</div><div>isig -icanon -iexten -echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke</div></div><div><br></div><div>And tty1 after exiting plymouth:</div>
<div><div>root@000c29af1815:~# plymouth quit</div><div>root@000c29af1815:~# stty -a --file=/dev/tty1</div><div>speed 38400 baud; rows 30; columns 80; line = 0;</div><div>intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z;</div>
<div>rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;</div><div>-parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts</div><div>-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel iutf8</div>
<div>opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0</div><div>isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke</div></div><div><br></div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
after the keyboard is stolen away but before qutting plymouth? Also<br>
the output of<br>
<br>
ls -l /proc/$(/sbin/pidof plymouthd)/fd<br></blockquote><div> </div><div><div>root@000c29af1815:~# ls -l /proc/250/fd</div><div>total 0</div><div>lrwx------ 1 root root 64 2010-09-28 21:19 0 -> /dev/console (deleted)</div>
<div>lrwx------ 1 root root 64 2010-09-28 21:19 1 -> /dev/console (deleted)</div><div>lrwx------ 1 root root 64 2010-09-28 21:19 10 -> /dev/tty1</div><div>lrwx------ 1 root root 64 2010-09-28 21:19 2 -> /dev/console (deleted)</div>
<div>lrwx------ 1 root root 64 2010-09-28 21:19 3 -> anon_inode:[eventpoll]</div><div>lr-x------ 1 root root 64 2010-09-28 21:19 4 -> pipe:[1922]</div><div>l-wx------ 1 root root 64 2010-09-28 21:19 5 -> pipe:[1922]</div>
<div>lrwx------ 1 root root 64 2010-09-28 21:19 6 -> /dev/ptmx</div><div>lrwx------ 1 root root 64 2010-09-28 21:19 7 -> /dev/tty1</div><div>lrwx------ 1 root root 64 2010-09-28 21:19 8 -> socket:[1927]</div><div>
lrwx------ 1 root root 64 2010-09-28 21:19 9 -> /dev/fb0</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
would be useful. I may have to do a debian install and try to<br>
reproduce to make head way on this issue though. If I do go that<br>
route, tips on how to recreate your reproduction environment would be<br>
useful.</blockquote><div><br></div><div>Mmhh. This is really going to be difficult. See, I have a live distro with some proprietary software in, a lot of customs packages, in a prototype form, that is built with a complex sequence of Makefiles and scripts... Mostly is ressembles a debian squeeze and a debian-live initramfs. Also, it lacks many packages and typical binaries found on a normal distro, the user will never see a shell on it, it is mostly remote-controlled by a cluster admin CLI.</div>
<div><br></div><div>But I'd be glad to help as much as I can.</div></div><br clear="all">Regards,<br>-- <br>Jérôme Martin<br>
</div>