Bug 128566 - irqs are disabled
Summary: irqs are disabled
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-26 15:28 UTC by Roger Durañona
Modified: 2015-01-04 22:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-04-16 04:19:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Roger Durañona 2004-07-26 15:28:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.6) Gecko/20040510

Description of problem:
I assing this bug to kernel, but Im not sure if could be caused by
another compnent.
The system starts disabling IRQs few minutes after is is restarted.
Usually disables 9, 5 and low numbers first. Given enough time,
disables irq 177 (assigned to eth1) and maybe some others I havent
noticed yet.
My hardware is
AOpen dx34 plus mb, 2 P3 CPUs (800Mhz), 256 MbRAM
1 HD scsi 19GB
2 HD ide 80Mb, 60 Mb
1 ide CD Writer 
Audigy 1 soundcard
1 onboard intel eth card, 2 8139 eht cards.
ATI radeon 7000 with DRI drivers
running smp kernel


Version-Release number of selected component (if applicable):
kernel-2.6.5-1.358

How reproducible:
Always

Steps to Reproduce:
1. Start the system
2.
3.
    

Actual Results:  In a few minutes, IRQ 5,  9 or both are disabled.
Only a waring message is shown, no error cause is displayed.

Additional info:

Comment 1 Dave Jones 2005-04-16 04:19:00 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.



Note You need to log in before you can comment on or make changes to this bug.