Fwd: Re: [Voyage-linux] nodma Kernel Option (still) Not Working
Miroslav Machala
(spam-protected)
Thu Jul 29 14:23:16 HKT 2010
Hello,
can someone please confirm the ide=nodma option works for them in the stock voyage 0.6.5 kernel on WRAP boards?
I have the following in my /boot/grub/menu.lst:
kernel /vmlinuz root=LABEL=ROOT_FS console=ttyS0,38400n8 ide=nodma
This is what I was using for years in Voyage up to 0.5, starting 0.6 (and in 0.6.5 as well) it does not work anymore and the system is still waiting for DMA timeouts.
This is my output during boot:
---output omitted---
0.000000] Allocating PCI resources starting at 10000000 (gap: 8000000:f8000000)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32415
[ 0.000000] Kernel command line: root=LABEL=ROOT_FS console=ttyS0,38400n8 ide=nodma
[ 0.000000] Initializing CPU#0
[ 0.000000] NR_IRQS:288
---output omitted---
[ 18.131023] Probing IDE interface ide0...
[ 18.394752] hda: CF CARD 4GB, CFA DISK drive
[ 18.705029] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[ 18.705183] hda: UDMA/33 mode selected
[ 18.706684] Probing IDE interface ide1...
[ 19.229024] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 (serialized)
[ 19.231645] ide1 at 0x170-0x177,0x376 on irq 15 (serialized)
[ 19.238422] hda: max request size: 128KiB
[ 19.238593] hda: 7806960 sectors (3997 MB) w/1KiB Cache, CHS=7745/16/63
[ 19.250963] hda: cache flushes supported
[ 19.252397] hda:<4>hda: ide_dma_sff_timer_expiry: DMA status (0x21)
[ 49.247920] hda: DMA timeout error
[ 49.248882] ide_dma_end dma_stat=21 err=1 newerr=0
[ 49.248882] hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
[ 49.248882] hda: possibly failed opcode: 0xc8
[ 49.248882] hda: DMA disabled
[ 49.297913] ide0: reset: success
[ 49.311927] hda1
[ 69.668809] hda: ide_dma_sff_timer_expiry: DMA status (0x21)
[ 79.667282] hda: DMA timeout error
[ 79.668243] ide_dma_end dma_stat=21 err=1 newerr=0
[ 79.668243] hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
[ 79.668243] hda: possibly failed opcode: 0xc8
[ 79.668243] hda: DMA disabled
[ 79.717275] ide0: reset: success
[ 99.730225] hda: ide_dma_sff_timer_expiry: DMA status (0x21)
[ 109.728697] hda: DMA timeout error
[ 109.729658] ide_dma_end dma_stat=21 err=1 newerr=0
[ 109.729658] hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
[ 109.729658] hda: possibly failed opcode: 0xc8
[ 109.729658] hda: DMA disabled
[ 109.778690] ide0: reset: success
[ 129.789640] hda: ide_dma_sff_timer_expiry: DMA status (0x21)
[ 139.788112] hda: DMA timeout error
[ 139.789073] ide_dma_end dma_stat=21 err=1 newerr=0
[ 139.789073] hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
[ 139.789073] hda: possibly failed opcode: 0xc8
[ 139.789073] hda: DMA disabled
[ 139.838104] ide0: reset: success
[ 145.728569] udevd version 125 started
Thank you very much in advance for any help.
Best regards,
MM
# ------------ Původní zpráva ------------
# Od: Miroslav Machala <Machala.M at seznam.cz>
# Komu: Kim-man 'Punky' TSE<punkytse at punknix.com>,
# Kopie: <voyage-linux at voyage.hk>,
# Předmět: Re: [Voyage-linux] nodma Kernel Option (still) Not Working
# Datum: 23.7.2010 16:26:26
# ----------------------------------------
# Hi,
#
# that's exactly what I'm doing and what I was using with Voyage 0.5 and below
# without any issue. Since 0.6 (and in 0.6.5 as well) it does not work anymore.
#
# Does ide=nodma kernel boot parameter work for anyone in 0.6.5?
#
# Regards
#
# MM
#
# > ------------ Původní zpráva ------------
# > Od: Kim-man 'Punky' TSE <punkytse at punknix.com>
# > Předmět: Re: [Voyage-linux] nodma Kernel Option (still) Not Working
# > Datum: 23.7.2010 13:11:07
# > ----------------------------------------
# > Hi,
# >
# > Perhaps adding "ide=nodma" to kernel boot parameter in /boot/grub/menu.lst is
# > better.
# >
# > - Punky
# >
# > On 7/23/2010 3:31 PM, Miroslav Machala wrote:
# > > Hello,
# > >
# > > I encountered an issue with the nodma kernel option not working with WRAP.
# > It's an issue that apparently some have laready been dealing with as the
# > following threat suggests:
# > >
# > > http://comments.gmane.org/gmane.linux.distributions.voyage.general/2811
# > >
# > > Apparently the issue is that ide is not compiled into the kernel. There are
# > two options:
# > >
# > > 1. run the following:
# > > remountrw
# > > echo 'options ide_core options="ide=nodma"'> /etc/modprobe.d/ide
# > > update-initramfs -u
# > > remountro
# > >
# > > to update the init image with the nodma option passed to the module.
# Although
# > I do not know the reason, this does not work for me with the latest voyage
# > release (0.6.5). The system still waits with those DMA expiry messages and
# the
# > boot takes quite a long time.
# > >
# > > 2. Have the kernel recompiled with ide compiled in. Unfortunately the
# kernels
# > provided under the thread above are no longer available and the ones that are
# > currently under "experimental" directory do not change anything with respcet
# to
# > the nodma option.
# > >
# > > Is there any other solution or would it be possible to provide a voyage
# kernel
# > with ide complied in?
# > >
# > > Thank you very much.
# > >
# > > Regards,
# > >
# > > MM
# > >
# > > _______________________________________________
# > > Voyage-linux mailing list
# > > Voyage-linux at list.voyage.hk
# > > http://list.voyage.hk/mailman/listinfo/voyage-linux
# >
# >
# > --
# > Regards,
# > Punky
# >
# > Voyage Solutions (http://solution.voyage.hk)
# > * Embedded Solutions and Systems
# > - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
# > - Network Engineering, Development Platform and Consultation
# >
# >
# >
# >
# >
# >
#
More information about the Voyage-linux
mailing list