CentOS Bug Tracker
CentOS Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002623CentOS-5kernelpublic2008-01-25 06:122009-02-24 15:05
Reporteretbe 
PrioritynormalSeveritycrashReproducibilityalways
StatusfeedbackResolutionopen 
PlatformOSOS Version
Product Version5.1 
Target VersionFixed in Version 
Summary0002623: ide=nodma causes a kernel panic
DescriptionI'm running an x86_64 system with kernel 2.6.18-53.el5. /dev/hda (the only mass storage device) is an ATA adapter for a SD flash card, I suspect that it's bridged from a SATA controller on the motherboard.

When DMA is enabled the machine usually hangs, if it doesn't hang then eventually the kernel resets the interface with DMA turned off. If I have the first line of /etc/rc.sysinit be "hdparm -c1 -d0 /dev/hda" then everything works well. If I try to use "ide=nodma" on the kernel command line then I get the following during the boot process:

Loading ext3.ko NMI Watchdog detected LOCKUP on CPU 0
CPU 0
Modules linked in: jbd ehci_hcd ohci_hcd uhci_hcd
Pid: 356, comm: init Not tainted 2.6.18-53.el5 #1
RIP: 0010:[<ffffffff80062b7c>] [<ffffffff80062b7c>] .text.lock.spinlock+0x2/0x30
RSP: 0018:ffffffff8040df30 EFLAGS: 00000086
RAX: 00000005e6c0a1bf RBX: ffff81007e844080 RCX: ffff810002376478
RDX: 00000005e6c08fd3 RSI: 00000005e6c083f7 RDI: ffff810002376400
RBP: ffffffff8040df68 R08: ffffffff80404400 R09: ffff810081f72000
R10: ffff8100026d1f58 R11: ffffffff8005b116 R12: ffff81007e844080
R13: ffff810002376400 R14: ffff810002376400 R15: 0000000000511350
FS: 000000000ca2c8f0(0063) GS:ffffffff80396000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000ca37028 CR3: 000000007ea03000 CR4: 00000000000006e0
Process init (pid: 356, threadinfo ffff81007eb7e000, task ffff81007e844080)
Stack: ffffffff80089256 0000000080011cb4 ffff81007e844080 0000000000000000
 0000000000000000 ffff810002376400 0000000000511350 0000000000000000
 ffffffff800930fc ffff81007eb7fea8 ffff81007eb7fed0 ffff81007e889ac0
Call Trace:
 <IRQ> [<ffffffff80089256>] scheduler_tick+0xc3/0x357
 [<ffffffff800930fc>] update_process_times+0x5c/0x68
 [<ffffffff800746e3>] smp_local_timer_interrupt+0x23/0x47
 [<ffffffff80074da5>] smp_apic_timer_interrupt+0x41/0x47
 [<ffffffff8005bc8e>] apic_timer_interrupt+0x66/0x6c
 <EOI> [<ffffffff8005b116>] system_call+0x7e/0x83
 [<ffffffff8005b007>] ret_from_fork+0x7/0x25


Code: 83 3f 00 7e f9 e9 7f fe ff ff f3 90 83 3f 00 7e f9 e9 f9 fe
Kernel panic - not syncing: nmi watchdog

CentOS release 5 (Final)
Kernel 2.6.18-53.el5 on an x86_64
Additional Informationprocessor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 22
model name : Intel(R) Celeron(R) CPU 420 @ 1.60GHz
stepping : 1
cpu MHz : 1607.219
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm syscall nx lm constant_tsc up pni monitor ds_cpl tm2 cx16 xtpr lahf_lm
bogomips : 3216.92
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0008843)
tru (administrator)
2009-02-24 15:05

do you still have the pb on 2.6.18-92.1.22.el5 ?

- Issue History
Date Modified Username Field Change
2008-01-25 06:12 etbe New Issue
2009-02-24 15:05 tru Note Added: 0008843
2009-02-24 15:05 tru Status new => feedback


Copyright © 2000 - 2014 MantisBT Team
Powered by Mantis Bugtracker