Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 158374 - soft lockup detected on CPU#0 catches ide_dma_test_irq
Summary: soft lockup detected on CPU#0 catches ide_dma_test_irq
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-21 05:08 UTC by Tom Mitchell
Modified: 2015-01-04 22:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-09-26 22:00:01 UTC

Attachments (Terms of Use)
Unedited console info. (deleted)
2005-05-21 05:10 UTC, Tom Mitchell
no flags Details
Second console capture... (deleted)
2005-05-22 01:45 UTC, Tom Mitchell
no flags Details
ttyS0/console capture of the error (deleted)
2005-07-02 17:17 UTC, Tom Mitchell
no flags Details

Description Tom Mitchell 2005-05-21 05:08:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
without ide=nodma  I observed this on  2.6.11-1.1323_FC4 (
Call Trace: <#MC> <ffffffff8013a3f5>{panic+133} <ffffffff80116d28>{print_mce+136}
       <ffffffff80116df9>{mce_panic+137} <ffffffff801173d2>{do_machine_check+754}
       <ffffffff802fd710>{ide_dma_intr+0} <ffffffff80110127>{machine_check+127}
       <ffffffff802fd710>{ide_dma_intr+0} <ffffffff802fdd20>{__ide_dma_test_irq+0}
       <ffffffff802f5104>{ide_inb+4}  <EOE>  <IRQ> <ffffffff802fdd38>{__ide_dma_test_irq+24}
       <ffffffff802f44c0>{ide_intr+880} <ffffffff8017017c>{handle_IRQ_event+44}
       <ffffffff8017038d>{__do_IRQ+477} <ffffffff8013c49e>{profile_tick+78}
       <ffffffff80112098>{do_IRQ+72} <ffffffff8010f6a3>{ret_from_intr+0}
        <EOI> <ffffffff8010d230>{default_idle+0} <ffffffff8010d252>{default_idle+34}
       <ffffffff8010d291>{cpu_idle+49} <ffffffff805847e5>{start_kernel+469}
 Badness in panic at kernel/panic.c:119 (Tainted: G   M )

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

How reproducible:

Steps to Reproduce:
1. x86_64 and Kernel command line: ro root=/dev/VolGroup00/LogVol00  console=tty0 console=ttyS0,9600 debug acXpi=oXff aXgp=oXff iXde=nXodma

2. boot...

3. Panics too often... so I still have the easy to edit flags handsy

Actual Results:  Kernel panic - not syncing: Machine check

Call Trace: <#MC> <ffffffff8013a3f5>{panic+133} <ffffffff80116d28>{print_mce+136}

Expected Results:   login:
Fedora Core release 3.91 (Pre-FC4)
Kernel 2.6.11-1.1323_FC4 on an x86_64

Additional info:

I will attach more console info in a moment.

Comment 1 Tom Mitchell 2005-05-21 05:10:54 UTC
Created attachment 114659 [details]
Unedited console info.


Comment 2 Dave Jones 2005-05-21 06:41:21 UTC
machine check exceptions are usually a sign of hardware going bad.
Try running memtest for a few hours.

Comment 3 Tom Mitchell 2005-05-22 01:45:27 UTC
Created attachment 114680 [details]
Second console capture...

After eight hours of memtest.
Another panic

Comment 4 Dave Jones 2005-06-27 23:19:47 UTC
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done


Comment 5 Tom Mitchell 2005-07-02 17:14:58 UTC
Reproduced on FC4 released
 Note that the system will run with ide=nodma

Comment 6 Tom Mitchell 2005-07-02 17:17:03 UTC
Created attachment 116292 [details]
ttyS0/console  capture of the error

Comment 7 Dave Jones 2005-07-15 21:39:13 UTC
[This comment has been added as a mass update for all FC4 kernel bugs.
 If you have migrated this bug from an FC3 bug today, ignore this comment.]

Please retest your problem with todays 2.6.12-1.1398_FC4 update.

If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..

mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak

Thank you.

Comment 8 Dave Jones 2005-09-26 22:00:01 UTC
softlockup disabled in latest errata.

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