From: Steve Rottinger <steve@pentek.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.18 Hard lockup advice needed: do_IRQ: stack overflow 508
Date: Wed, 18 Oct 2006 11:50:20 -0400 [thread overview]
Message-ID: <45364D3C.3070204@pentek.com> (raw)
Hi,
I have a small Pentium 4 file server set up using version 2.6.18 of the Kernel. The system contains a
SiI 3124 based SATA controller, and I have a software RAID set up, with LVM enabled. During normal daily operation, the system is stable. However, when I perform nightly backups, and there is a lot of disk and network activity, as the data is transferred to a backup server, the system eventually locks up. Unfortunately, there is no indication of a failure in the system logs. I also enabled the NMI_Watchdog without any additional visibility. By disabling the screen blanking on the console windows, I do get a single message reported before the lockup:
do_IRQ: stack overflow 508
do_IRQ+0x69/0xbc 0xc0104ce4
If I downgrade to 2.6.17 of the Kernel, I see the same problem, but it takes longer for it to occur.
-Steve
next reply other threads:[~2006-10-18 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 15:50 Steve Rottinger [this message]
2006-10-19 9:44 ` 2.6.18 Hard lockup advice needed: do_IRQ: stack overflow 508 Jarek Poplawski
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=45364D3C.3070204@pentek.com \
--to=steve@pentek.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