From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 Description of problem: After upgrading to the 2.4.18 series kernels from 2.4.9-12 our http://supermicro.com/PRODUCT/MotherBoards/RCC_LE/370dl3.htm dual Pentium 3 machine has been leaving 'wait_on_irq' oops in the logs for both processors, the ksoftirqd_CPU[0-1] processes have been racking up abnormal quantities of time, and the machine will go unresponsive to the keyboard for tens of seconds at a time. We've swapped out the CPUs, memory, broken an IDE software raid, and tried various kernels in the 2.4.18 series (currently running 2.4.18-24.7.xsmp) all to no avail. How reproducible: Always Steps to Reproduce: 1. shutdown machine 2. reboot Actual Results: If one waits for about a hour, things start going south in terms of keyboard responsiveness. Then every few days it'll drop an oops in the log and the keyboard responsiveness will progressively get worse. Expected Results: No hesitations or oops
Created attachment 90284 [details] an unclean ksymoops
can you post a dmesg of the machine ?
Created attachment 90293 [details] dmesg w/o an oops The machine's only been up 12 hours and hasn't lobbed an oops yet.
one interesting test would be to use aic7xxx_old instead of aic7xxx 2.4.9 used the old driver by default
Created attachment 90375 [details] A dmesg after a longer period of uptime Here's a dmesg after 3 days worth of uptime and we now have 54:13 ksoftirqd_CPU0 66:58 ksoftirqd_CPU1
Is there a "step by step" somewhere for trying the aic7xxx swap?
Replaced the last piece of hardware: the motherboard, and still the same "wait_on_irq" oops. <sigh>
Created attachment 91059 [details] ksymoops output of recent oops
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/