> -----Original Message----- > From: Nikita V. Youshchenko [mailto:yoush@xxxxxxxxx] > Sent: Saturday, November 21, 2009 2:26 AM > To: Leyendecker, Robert > Cc: rt-users > Subject: Re: help needed, 2.6.31.6-rt19 hang with network user app > > > > Does host A have a serial port? If yes, connect that to another > host > > > using a null-modem cable, boot host A with serial console (boot arg > > > console=ttyS0,15200), and use that to extract kernel crash message. > > > Then post that to this list. > > > > unfortunately - nothing shows up in the serial log after the normal > boot > > spew. I do see some sort of cr/lf every second for a while. > > Of course that should be console=ttyS0,115200 > And on other side serial communication software should be configured > to use 115200 8n1 with no flow control. No problem, I caught that. During boot, console messages are displayed in tty and it looks normal, after boot tty is quiet. I'll look at it some more because it would be very nice to have the console working. Are the regular tty HUPs a result of failed auto baud detect? > > > Nov 20 21:12:00 localhost kernel: BUG: using smp_processor_id() in > preemptible [00000000] code: smash/6801 > > Nov 20 21:12:00 localhost kernel: caller is __schedule+0xe/0x7d4 Nov > 20 21:12:00 localhost kernel: Pid: 6801, comm: smash Not tainted > 2.6.31.6-rt19 #1 > > Nov 20 21:12:00 localhost kernel: Call Trace: > > Nov 20 21:12:00 localhost kernel: [<c06dc3df>] ? printk+0xf/0x18 > > Nov 20 21:12:00 localhost kernel: [<c05499a6>] > debug_smp_processor_id+0xa6/0xbc > > Nov 20 21:12:00 localhost kernel: [<c06dc689>] __schedule+0xe/0x7d4 > > Nov 20 21:12:00 localhost kernel: [<c046621f>] ? > audit_syscall_exit+0xfa/0x10f > > Nov 20 21:12:00 localhost kernel: [<c040a955>] ? > syscall_trace_leave+0xc8/0xef > > Nov 20 21:12:00 localhost kernel: [<c040338a>] work_resched+0x5/0x19 > > Hopely somebody on list will be able to comment on this. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
