Bug 80279
Summary: | ksoftirqd_CPU0 hits 100% when running iostat | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Anthony Marusic <amarusic> |
Component: | kernel | Assignee: | Don Howard <dhoward> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | jeffrey.buchsbaum, nphilipp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-26 18:12:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Anthony Marusic
2002-12-23 22:08:21 UTC
This is the same bug really as 83789. I have the same problem with just one telnet session running. Dell 530 dual 2.4ghz 4gb ram ecc Im unconvinced they are the same thing 6 root 34 19 0 0 0 SWN 0.0 0.0 319:40 ksoftirqd_CPU0 10 root 15 0 0 0 0 SW 0.0 0.0 95:25 kswapd 13 root 15 0 0 0 0 SW 0.0 0.0 168:12 bdflush Linux 2.4.9-e.12enterprise #1 SMP Tue Feb 11 01:29:18 EST 2003 i686 unn This happens in a production environment running Oracle. Every few days the system will become completely unresponsive except for a redimentary functioning of the TCP/IP stack. Connect() returns success but remote host will just idle from that point forward. Server is unresponsive on console until it either returns (anywhere between 5 - 45 minutes, usually after the oracle listener and db have died) or the host is manually powercycled. Note: this is not connected with any orinico problems. Does the problem still show with recent kernels? Anyway, this sounds like a kernel/scheduling problem to me, even more so because the problem shows not only when iostat runs. handing off to the kernel group this is an old one, i think we should start w/reproducing it on the latest rhel2.1 kernel, e.49. thanks. This is a truely ancient report. If there is no update here in the next two weeks demonstrating this bug on a current 2.1 kernel, this ticket will be closed. |