On Thu, 31 Aug 2000 16:23:08 +0200 (MET DST), Paul Wouters <paul@xtdnet.nl> wrote: >Lately I've been updating our smp machine, and alongside built a second >smp machine. The first one, apart from a "stuck on TLB" glitch two months ago >never crashed. >along with the entire machine. Today, I managed to get a logentry, though >ksymoops can't seem to read it (and I can't read/match the symbols for some >odd reason). > >Aug 31 16:28:49 dupla kernel: >Aug 31 16:28:49 dupla kernel: wait_on_bh, CPU 0: >Aug 31 16:28:49 dupla kernel: irq: 1 [0 1] >Aug 31 16:28:49 dupla kernel: bh: 1 [0 1] >Aug 31 16:29:20 dupla kernel: <[c010be9d]> <[c0169cc2]> <[c0169d3d]> <[c017990d]> <[c0151d6f]> <[c013496b]> <[c0134ac7]> stuck on TLB IPI wait (CPU#0) >Aug 31 16:29:20 dupla kernel: stuck on TLB IPI wait (CPU#0) >Aug 31 16:29:20 dupla kernel: stuck on TLB IPI wait (CPU#0) > >Ksymoops said: > >Warning (Oops_read): Code line not seen, dumping what data is available > >Trace; c010be9d <synchronize_bh+3d/50> >Trace; c0169cc2 <tcp_listen_poll+12/50> >Trace; c0169d3d <tcp_poll+3d/100> >Trace; c017990d <inet_poll+21/2c> >Trace; c0151d6f <sock_poll+1f/24> >Trace; c013496b <do_poll+7b/dc> >Trace; c0134ac7 <sys_poll+fb/17c> That trace matches the trace back on the stuck cpu. "Code line not seen" is normal when no Code: line is not printed, this trace type never contains a Code: line. >819 warnings and 1 error issued. Results may not be reliable. That points to a mismatch between the kernel and the System.map. You have to feed ksymoops the map and ksyms that correspond to the failing kernel. Like it says, the results might not be reliable. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
