From: "msrinath" <msrinath@bplitl.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel NMI error
Date: Tue, 16 Sep 2003 16:43:55 +0530 [thread overview]
Message-ID: <004c01c37c43$9ecaf4e0$1d03000a@srinath> (raw)
Hello Everybody,
Can anyone help me on this?
Recently one of our servers running RedHat linux 7.2 with 2.4.7-10 SMP
kernel generated the following log and the system rebooted. This system has
2 CPUs.
Sep 16 01:34:24 cbesc ftpd[30753]: FTP LOGIN FROM 16.128.157.7
[16.128.157.7], scuser
Sep 16 01:36:48 cbesc ftpd[30753]: FTP session closed
Sep 16 01:54:30 cbesc kernel: Uhhuh. NMI received for unknown reason 35.
Sep 16 01:54:30 cbesc kernel: Dazed and confused, but trying to continue
Sep 16 01:54:30 cbesc kernel: Do you have a strange power saving mode
enabled?
Sep 16 01:54:30 cbesc kernel: eth0: card reports no resources.
Sep 16 01:58:09 cbesc syslogd 1.4.1: restart.
Sep 16 01:58:09 cbesc syslog: syslogd startup succeeded
This is the first time we have faced this problem. The ethernet card used is
intel eepro 100. The details are shown below.
Sep 16 07:33:53 cbesc kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Sep 16 07:33:53 cbesc kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17
Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
Sep 16 07:33:53 cbesc kernel: eth0: Intel Corporation 82557 [Ethernet Pro
100], 00:A0:C9:A0:B7:71, IRQ 16.
Sep 16 07:33:53 cbesc kernel: Receiver lock-up bug exists -- enabling
work-around.
Sep 16 07:33:53 cbesc kernel: Board assembly 668081-004, Physical
connectors present: RJ45
Sep 16 07:33:53 cbesc kernel: Primary interface chip i82555 PHY #1.
Sep 16 07:33:54 cbesc kernel: General self-test: passed.
Sep 16 07:33:54 cbesc kernel: Serial sub-system self-test: passed.
Sep 16 07:33:54 cbesc kernel: Internal registers self-test: passed.
Sep 16 07:33:54 cbesc kernel: ROM checksum self-test: passed (0x3c15c8f1).
Sep 16 07:33:54 cbesc kernel: Receiver lock-up workaround activated.
Please let me know why this happened and whether it indicates any hardware
problem in the system.
Thanks & Regards,
- Srinath.
--
This message has been scanned for viruses and
dangerous content by Kaspersky on bpl Server, and is
believed to be clean.
bpl www.kaspersky.com
.
next reply other threads:[~2003-09-16 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 11:13 msrinath [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 11:38 Kernel NMI error msrinath
2003-09-16 13:25 ` Alan Cox
2003-09-17 9:51 ` msrinath
2003-09-17 13:41 ` Alan Cox
2003-09-18 3:52 ` msrinath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004c01c37c43$9ecaf4e0$1d03000a@srinath' \
--to=msrinath@bplitl.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox