kernel oopses
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Martin Siegert siegert at sfu.caMon Jan 21 18:13:44 PST 2002
- Previous message: Pentium4 cluster with Myrinet
- Next message: kernel oopses
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This is somewhat off topic - sorry for that. I am trying to use the linux driver for the SK9D21 GigE copper card on a RedHat 7.2 system with a 2.4.13 kernel. I have two athlon mp boxes with such a card connected with a cross-over cable. Running netpipe (NPtcp) from one box to the other causes a kernel oops. I am quite sure that the oops is due to the driver http://www.syskonnect.com/syskonnect/support/driver/htm/sk9dlin_2_4_13.htm (without that driver the kernel runs fine). The first thing I would like to do is to log the oops message. Right now it goes to the console only - it does not appear in the log files although syslog sends everything of severity *.info to /var/log/messages. /proc/kmsg is empty. There is a /proc/kcore file, but it is a binary file. I tried to read it using ksymoops, but it generates a huge amount of garbage on the screen but not the error message I see on the console. I have tried the -s option to klogd with no success either. Is there a way of getting the error message into a file (without typing it off the console screen)? Thanks for suggestions. Cheers, Martin ======================================================================== Martin Siegert Academic Computing Services phone: (604) 291-4691 Simon Fraser University fax: (604) 291-4242 Burnaby, British Columbia email: siegert at sfu.ca Canada V5A 1S6 ========================================================================
- Previous message: Pentium4 cluster with Myrinet
- Next message: kernel oopses
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
