Like the above folks, I have also experienced this issue. Twice in a row. <br><br>My hypervisor system:<br>Linux xencore 2.6.26-2-xen-amd64 #1 SMP Fri Mar 27 07:12:15 UTC 2009 x86_64 GNU/Linux<br># cat /etc/debian_version <br>
5.0.1<br><br>Guest:<br>Linux <a href="http://imrandev.soton.smoothwall.net">imrandev.soton.smoothwall.net</a> 2.6.26-2-xen-amd64 #1 SMP Fri Mar 27 07:12:15 UTC 2009 x86_64 GNU/Linux<br># cat /etc/debian_version <br>5.0.1<br>
<br>I noticed that this occured after I set BOOTLOGD_ENABLE=yes (formerly BOOTLOGD_ENABLE=no) in <br>/etc/default/bootlogd in my guest.<br><br>I was curious to see what boot up messages would be logged. There was probably no reason to do this since /var/log/boot only shows the default logging entry.<br>
<br>Below is what was shown on the xm console <guest> screen. When I connected this way I could not send any input to the terminal.<br><br>[46022.513876] ------------[ cut here ]------------<br>[46022.513890] kernel BUG at drivers/char/tty_io.c:811!<br>
[46022.513894] invalid opcode: 0000 [1] SMP <br>[46022.513897] CPU 0 <br>[46022.513900] Modules linked in: ipv6 nfs lockd nfs_acl sunrpc xt_tcpudp iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack ip_tables x_tables evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod thermal_sys<br>
[46022.513928] Pid: 882, comm: bootlogd Not tainted 2.6.26-2-xen-amd64 #1<br>[46022.513932] RIP: e030:[<ffffffff80359cad>] [<ffffffff80359cad>] tty_ldisc_put+0x34/0x5e<br>[46022.513941] RSP: e02b:ffff880007cc9e18 EFLAGS: 00010046<br>
[46022.513944] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000042<br>[46022.513947] RDX: 0000000000000000 RSI: 0000000000000003 RDI: ffffffff806000a4<br>[46022.513950] RBP: 0000000000000000 R08: 0000000000000008 R09: ffff880001db6200<br>
[46022.513953] R10: ffff880006bd2980 R11: 0000000000000003 R12: 0000000000000000<br>[46022.513955] R13: 0000000000000000 R14: 0000000000000000 R15: ffff8800065c2800<br>[46022.513962] FS: 00007f563095e6e0(0000) GS:ffffffff80539000(0000) knlGS:0000000000000000<br>
[46022.513965] CS: e033 DS: 0000 ES: 0000<br>[46022.513968] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br>[46022.513972] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400<br>[46022.513975] Process bootlogd (pid: 882, threadinfo ffff880007cc8000, task ffff880007d6aa80)<br>
[46022.513978] Stack: ffff8800065c2800 ffff880006bd2800 0000000000000000 ffffffff8035c7f0<br>[46022.513985] 0000000c38967ce0 0000000000000000 0000000207cc9f50 0000000006bd2800<br>[46022.513990] 0000000000000003 ffff880006646140 ffff880007c16080 ffff880007940150<br>
[46022.513995] Call Trace:<br>[46022.514000] [<ffffffff8035c7f0>] release_dev+0x546/0x5ce<br>[46022.514006] [<ffffffff80435bb7>] error_exit+0x0/0x69<br>[46022.514010] [<ffffffff8035c889>] tty_release+0x11/0x1a<br>
[46022.514015] [<ffffffff8028b13e>] __fput+0xa1/0x16b<br>[46022.514019] [<ffffffff8028885f>] filp_close+0x5d/0x65<br>[46022.514023] [<ffffffff80289bc9>] sys_close+0xa5/0x101<br>[46022.514027] [<ffffffff8020b528>] system_call+0x68/0x6d<br>
[46022.514031] [<ffffffff8020b4c0>] system_call+0x0/0x6d<br>[46022.514034] <br>[46022.514035] <br>[46022.514036] Code: ff 11 76 04 0f 0b eb fe 48 c7 c7 a4 00 60 80 e8 e8 b9 0d 00 48 89 c5 48 63 c3 48 69 d0 90 00 00 00 8b 82 48 01 60 80 85 c0 75 04 <0f> 0b eb fe 48 8b ba 40 01 60 80 ff c8 89 82 48 01 60 80 e8 d5 <br>
[46022.514083] RIP [<ffffffff80359cad>] tty_ldisc_put+0x34/0x5e<br>[46022.514087] RSP <ffff880007cc9e18><br>[46022.514093] ---[ end trace 9982d726e244ec38 ]---<br><br>I also had the following in my guest config:<br>
<br>## IC - added to prevent problems after upgrade to Debian Lenny<br>## See: <a href="http://maff.ailoo.net/2009/04/upgrade-from-debian-etch-xen-30-to-debian-lenny-xen-32-amd64/">http://maff.ailoo.net/2009/04/upgrade-from-debian-etch-xen-30-to-debian-lenny-xen-32-amd64/</a><br>
extra = "console=hvc0 xencons=tty"<br><br><br>Regards,<br>Imran Chaudhry<br>